From: Eli Zaretskii <eliz@gnu.org>
To: Lancelot SIX <lancelot.six@amd.com>
Cc: gdb-patches@sourceware.org, lsix@lancelotsix.com
Subject: Re: [PATCH v4] gdb/gcore: interrupt all threads before generating the corefile
Date: Tue, 06 Dec 2022 17:03:38 +0200 [thread overview]
Message-ID: <838rjk7ewl.fsf@gnu.org> (raw)
In-Reply-To: <20221206141248.2485033-1-lancelot.six@amd.com> (message from Lancelot SIX via Gdb-patches on Tue, 6 Dec 2022 14:12:48 +0000)
> CC: <lsix@lancelotsix.com>, Lancelot SIX <lancelot.six@amd.com>
> Date: Tue, 6 Dec 2022 14:12:48 +0000
> From: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
>
> Hi,
>
> Here is a V4 for https://sourceware.org/pipermail/gdb-patches/2022-November/193861.html
>
> Noticeable changes from V3:
>
> - Updated NEWS and documentation following Andrew's recommendations.
> - Fixed compatibility issues in the testcase.
> - Followed Andrew's recommendations on the gcore_command changes.
>
> All feedbacks are welcome.
Thanks, the documentation parts are OK.
next prev parent reply other threads:[~2022-12-06 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 14:12 Lancelot SIX
2022-12-06 15:03 ` Eli Zaretskii [this message]
2023-01-04 11:15 ` [PING] " Lancelot SIX
2023-01-06 21:27 ` Simon Marchi
2023-01-10 14:40 ` Lancelot SIX
2023-01-30 16:33 ` Lancelot SIX
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=838rjk7ewl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=lancelot.six@amd.com \
--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).