From: Pedro Alves <palves@redhat.com>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Handle vfork in thread with follow-fork-mode child
Date: Thu, 18 Apr 2019 16:17:00 -0000 [thread overview]
Message-ID: <76ba661b-e351-532f-f484-05bf6d727328@redhat.com> (raw)
In-Reply-To: <4f660e6e-4592-a5aa-418e-bb47ab62c603@suse.de>
On 4/18/19 4:48 PM, Tom de Vries wrote:
> I've tested this both with native and native-gdbserver and found no
> regressions.
>
> I've also verified that both blocks mentioned above are triggered by the
> new test-cases.
>
> LGTM.
>
Great, I've pushed it in, ...
>> From 575fecd185d07cd0d2f9d9aed5325e7b09b675e0 Mon Sep 17 00:00:00 2001
>> From: Pedro Alves <palves@redhat.com>
>> Date: Thu, 18 Apr 2019 09:57:45 +0100
>> Subject: [PATCH] [gdb] Handle vfork in thread with follow-fork-mode child
... after fixing the authorship back to you. Looks like squashing in
my fixes made stgit/git reset the author and I hadn't noticed.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-04-18 16:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 15:06 Tom de Vries
2019-04-17 17:45 ` Pedro Alves
2019-04-18 8:02 ` Tom de Vries
2019-04-18 9:12 ` Pedro Alves
2019-04-18 15:48 ` Tom de Vries
2019-04-18 16:17 ` Pedro Alves [this message]
2019-07-23 15:04 ` [8.3 backport] " Tom de Vries
2019-08-13 16:20 ` [PING][8.3 " Tom de Vries
2019-08-15 16:50 ` [8.3 " Pedro Alves
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=76ba661b-e351-532f-f484-05bf6d727328@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).