From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH 1/2] gdb: add inferior_cloned observable
Date: Thu, 14 Sep 2023 08:08:33 -0600 [thread overview]
Message-ID: <874jjwj19a.fsf@tromey.com> (raw)
In-Reply-To: <20230913152845.1540064-1-simon.marchi@efficios.com> (Simon Marchi via Gdb-patches's message of "Wed, 13 Sep 2023 11:28:37 -0400")
>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
Simon> The following patch makes the amdgpu port transfer a property from the
Simon> original inferior to the new inferior when using the clone-inferior
Simon> command. Add the inferior_cloned observable to help with this.
FWIW this patch seems totally fine to me.
Tom
next prev parent reply other threads:[~2023-09-14 14:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 15:28 Simon Marchi
2023-09-13 15:28 ` [PATCH 2/2] gdb/amdgpu: add precise-memory support Simon Marchi
2023-09-13 21:32 ` Lancelot SIX
2023-09-14 15:51 ` Simon Marchi
2023-09-14 14:10 ` Tom Tromey
2023-09-14 16:00 ` Simon Marchi
2023-09-14 16:18 ` Tom Tromey
2023-09-14 16:18 ` Simon Marchi
2023-09-14 14:08 ` Tom Tromey [this message]
2023-09-14 15:53 ` [PATCH 1/2] gdb: add inferior_cloned observable Simon Marchi
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=874jjwj19a.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--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).