This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Increase timeout on gdb.base/exitsignal.exp
- From: Pedro Alves <palves at redhat dot com>
- To: Sergio Durigan Junior <sergiodj at redhat dot com>
- Cc: GDB Patches <gdb-patches at sourceware dot org>
- Date: Tue, 25 Aug 2015 19:44:59 +0100
- Subject: Re: [PATCH] Increase timeout on gdb.base/exitsignal.exp
- Authentication-results: sourceware.org; auth=none
- References: <1440481342-25971-1-git-send-email-sergiodj at redhat dot com> <55DC46C5 dot 4050808 at redhat dot com> <87si77gr9x dot fsf at redhat dot com> <55DCB471 dot 4020103 at redhat dot com> <87oahvgqsl dot fsf at redhat dot com>
On 08/25/2015 07:35 PM, Sergio Durigan Junior wrote:
> On Tuesday, August 25 2015, Pedro Alves wrote:
>
>> 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:
>
> Oh, you're right, I missed that (don't know how) when I was creating the
> patch. Thanks for the catch; I'll update the patch.
I still don't think we should just bump the timeout for this without
understanding it better. It very much looks like to me there's
a bug somewhere. I see that it sometimes fails on the x86 buildbots too:
http://gdb-build.sergiodj.net/builders/Fedora-x86_64-native-extended-gdbserver-m32/builds/1805
Thanks,
Pedro Alves