From: Lancelot SIX <Lancelot.Six@amd.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, lsix@lancelotsix.com
Subject: Re: [PATCH v6 3/3] gdb/gcore: interrupt all threads to generate core in non-stop targets
Date: Wed, 10 May 2023 20:08:12 +0100 [thread overview]
Message-ID: <d84a969e-b7d7-39d5-0b97-bc47f162fc80@amd.com> (raw)
In-Reply-To: <83bkis6m8j.fsf@gnu.org>
>> Date: Wed, 10 May 2023 19:46:36 +0100
>> Cc: lsix@lancelotsix.com
>> From: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
>>
>> Hi,
>>
>> Kindly pinging on this patch.
>
> I believe I already reviewed the documentation parts, yes?
Hi,
Yes you have. There was just a remark about a missing cross-reference
which I have since added locally
(https://sourceware.org/pipermail/gdb-patches/2023-March/198220.html).
I wanted to check if the rest of the series needed other modification
before sending a full new revision.
Thanks,
Lancelot.
prev parent reply other threads:[~2023-05-10 19:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 16:51 [PATCH v5] gdb/gcore: interrupt all threads before generating the corefile Lancelot SIX
2023-02-10 14:36 ` [PING] " Lancelot SIX
2023-02-10 21:46 ` Simon Marchi
2023-03-22 16:35 ` [PATCH v6 0/3] interrupt all threads to generate core in non-stop targets Lancelot SIX
2023-03-22 16:35 ` [PATCH v6 1/3] gdb: add inferior parameter to target_is_non_stop_p Lancelot SIX
2023-03-22 16:35 ` [PATCH v6 2/3] gdb/infrun: Improve assertion in stop_all_threads Lancelot SIX
2023-03-22 16:35 ` [PATCH v6 3/3] gdb/gcore: interrupt all threads to generate core in non-stop targets Lancelot SIX
2023-03-22 16:44 ` Eli Zaretskii
2023-03-22 16:59 ` Lancelot SIX
2023-05-10 18:46 ` Lancelot SIX
2023-05-10 19:05 ` Eli Zaretskii
2023-05-10 19:08 ` Lancelot SIX [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=d84a969e-b7d7-39d5-0b97-bc47f162fc80@amd.com \
--to=lancelot.six@amd.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.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).