From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Increase timeout on gdb.base/exitsignal.exp
Date: Tue, 25 Aug 2015 18:35:00 -0000 [thread overview]
Message-ID: <87oahvgqsl.fsf@redhat.com> (raw)
In-Reply-To: <55DCB471.4020103@redhat.com> (Pedro Alves's message of "Tue, 25 Aug 2015 19:31:13 +0100")
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.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2015-08-25 18:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 5:42 Sergio Durigan Junior
2015-08-25 10:43 ` Pedro Alves
2015-08-25 18:24 ` Sergio Durigan Junior
2015-08-25 18:31 ` Pedro Alves
2015-08-25 18:35 ` Sergio Durigan Junior [this message]
2015-08-25 18:45 ` Pedro Alves
2015-08-25 19:09 ` Peter Schauer
2015-08-25 19:13 ` Sergio Durigan Junior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oahvgqsl.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox