From: Pedro Alves <palves@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Avoid gdb.base/fork-running-state.exp lingering processes (Re: [gdb/testsuite] Fix hang in fork-running-state.c)
Date: Thu, 14 Jun 2018 16:44:00 -0000 [thread overview]
Message-ID: <5e9a729d-07ee-2385-fd47-f929436dadf0@redhat.com> (raw)
In-Reply-To: <81f5ddc0-e521-07d8-f378-6e12d7e7f529@suse.de>
On 06/14/2018 05:06 PM, Tom de Vries wrote:
> On 06/14/2018 02:59 PM, Pedro Alves wrote:
>> Like so?
>>
>
> I tried it out, and it works for me.
>
> The approach looks ok to me.
>
Great, I'll push it in in a bit.
> I guess the alarms (180) calls are no longer necessary?
It's better to still have them, in case something goes wrong,
gdb crashes or the test fails, etc.
Thanks,
Pedro Alves
prev parent reply other threads:[~2018-06-14 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 15:51 [gdb/testsuite] Fix hang in fork-running-state.c Tom de Vries
2018-06-13 12:10 ` Pedro Alves
2018-06-14 12:59 ` [PATCH] Avoid gdb.base/fork-running-state.exp lingering processes (Re: [gdb/testsuite] Fix hang in fork-running-state.c) Pedro Alves
2018-06-14 16:07 ` Tom de Vries
2018-06-14 16:44 ` Pedro Alves [this message]
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=5e9a729d-07ee-2385-fd47-f929436dadf0@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).