[PATCH] Handle additional connection error
Luis Machado
luis.machado@linaro.org
Thu Jan 21 20:12:22 GMT 2021
On 1/21/21 5:05 PM, Simon Marchi wrote:
>
>
> On 2021-01-21 2:58 p.m., Luis Machado via Gdb-patches wrote:
>> On Ubuntu 18.04/20.04 I was running into annoying timeouts for
>> gdb.server/server-connect.exp. Those were caused by the ipv6 tests, because
>> they were running into the "Cannot assign requested address" error.
>>
>> Improve this by handling this additional error in the testsuite library.
>>
>> It still fails for me, but at least it fails pretty quickly and doesn't make the
>> testsuite run take longer.
>>
>> gdb/testsuite/ChangeLog:
>>
>> YYYY-MM-DD Luis Machado <luis.machado@linaro.org>
>>
>> * lib/gdbserver-support.exp (gdb_target_cmd_ext): Handle a new error
>> message.
>> ---
>> gdb/testsuite/lib/gdbserver-support.exp | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/gdb/testsuite/lib/gdbserver-support.exp b/gdb/testsuite/lib/gdbserver-support.exp
>> index 0cec39dbefc..7b48b5a8399 100644
>> --- a/gdb/testsuite/lib/gdbserver-support.exp
>> +++ b/gdb/testsuite/lib/gdbserver-support.exp
>> @@ -64,6 +64,9 @@ proc gdb_target_cmd_ext { targetname serialport {additional_text ""} } {
>> -re "Couldn't establish connection to remote.*$gdb_prompt $" {
>> verbose "Connection failed"
>> }
>> + -re "Cannot assign requested address.*$gdb_prompt $" {
>> + verbose "Could not assign requested address"
>> + }
>> -re "Non-stop mode requested, but remote does not support non-stop.*$gdb_prompt $" {
>> verbose "remote does not support non-stop"
>> return 1
>>
>
> That looks good to me, but out of curiosity, which syscall fails with that error (EADDRNOTAVAIL)?
connect does. I'm not entirely sure why, but I think it might be related
to the system configuration. It's been this way for a while, but I
finally got annoyed enough to address it.
I'll push this one shortly. Thanks!
>
> Simon
>
More information about the Gdb-patches
mailing list