[PATCH] Increase timeout on gdb.base/exitsignal.exp
Pedro Alves
palves@redhat.com
Tue Aug 25 18:31:00 GMT 2015
On 08/25/2015 07:24 PM, Sergio Durigan Junior wrote:
>> This (many instances) doesn't make sense to me. And I think wouldn't
>> fix anything. Seems to me the bumped timeout, if any, should be around
>> the continue that caused the first time out:
>>
>> # Continue until the end.
>> gdb_test "continue" "Program terminated with signal SIGSEGV.*" \
>> "program terminated with SIGSEGV"
>
> Sorry, I am confused... The timeout does not occur on this command: it
> occurs on the print commands. So I think we must extend the timeout for
> the print commands; don't we?
Not AFAICS from what you pasted. The print time outs seem to me to be
cascading fails. Highlighting what you pasted:
(gdb) PASS: gdb.base/exitsignal.exp: $_exitcode is void before running
continue
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x00003fffb7cbf808 in .raise () from target:/lib64/libc.so.6
(gdb) PASS: gdb.base/exitsignal.exp: trigger SIGSEGV
continue
Continuing.
FAIL: gdb.base/exitsignal.exp: program terminated with SIGSEGV (timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
print $_exitsignal
FAIL: gdb.base/exitsignal.exp: $_exitsignal is 11 (SIGSEGV) after SIGSEGV. (timeout)
print $_exitcode
FAIL: gdb.base/exitsignal.exp: $_exitcode is still void after SIGSEGV (timeout)
kill
Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) print $_exitsignal
$3 = 11
(gdb) print $_exitcode
$4 = void
That timed out waiting for the "Program terminated with signal SIGSEGV"
output. Stripping the prints, we see it more clearly:
Program received signal SIGSEGV, Segmentation fault.
0x00003fffb7cbf808 in .raise () from target:/lib64/libc.so.6
(gdb) PASS: gdb.base/exitsignal.exp: trigger SIGSEGV
continue
Continuing.
FAIL: gdb.base/exitsignal.exp: program terminated with SIGSEGV (timeout)
Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb)
Thanks,
Pedro Alves
More information about the Gdb-patches
mailing list