From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH] gdb: test vfork + follow-fork-mode=parent + detach-on-fork=off
Date: Thu, 31 Mar 2022 11:14:17 -0400 [thread overview]
Message-ID: <dac1c18a-bd4b-8184-44fa-eb24d91dce11@polymtl.ca> (raw)
In-Reply-To: <2215b471-ab92-02bf-597b-d9647d269046@palves.net>
On 2022-03-31 07:47, Pedro Alves wrote:
> On 2022-01-10 17:50, Simon Marchi via Gdb-patches wrote:
>> From: Simon Marchi <simon.marchi@efficios.com>
>>
>> The particular behavior we have when using that combination of settings
>> doesn't seem tested at all (at least, I don't find it if I grep for "Can
>> not resume the parent process"). Add a simple test for that.
>
> Huh, wow, guilty as charged.
>
> LGTM.
>
> Remember to update copyright years.
Done, thanks!
Simon
prev parent reply other threads:[~2022-03-31 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 17:50 Simon Marchi
2022-03-31 11:47 ` Pedro Alves
2022-03-31 15:14 ` Simon Marchi [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=dac1c18a-bd4b-8184-44fa-eb24d91dce11@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=simon.marchi@efficios.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).