From: Tom Tromey <tom@tromey.com>
To: John Baldwin <jhb@FreeBSD.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 0/4] Handle null inferiors in target::read_description
Date: Fri, 07 Jul 2023 10:15:17 -0600 [thread overview]
Message-ID: <87pm53snoq.fsf@tromey.com> (raw)
In-Reply-To: <20230706172337.39099-1-jhb@FreeBSD.org> (John Baldwin's message of "Thu, 6 Jul 2023 10:23:33 -0700")
>>>>> "John" == John Baldwin <jhb@FreeBSD.org> writes:
John> Change since V1:
John> - Call the beneath target's read_description method instead of
John> returning nullptr.
FWIW, I read through these. I didn't see any red flags, but then again,
I'm not sure I really understand the underlying scenario very well.
I didn't want this to go un-answered, though. IMO it is ok.
Tom
prev parent reply other threads:[~2023-07-07 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 17:23 John Baldwin
2023-07-06 17:23 ` [PATCH v2 1/4] *-fbsd-nat: Handle null inferior in read_description John Baldwin
2023-07-06 17:23 ` [PATCH v2 2/4] *-linux-nat: " John Baldwin
2023-07-06 17:23 ` [PATCH v2 3/4] Add a have_native_target helper function for use with require John Baldwin
2023-07-06 17:23 ` [PATCH v2 4/4] Test that native targets can read a tdesc without a process attached John Baldwin
2023-07-07 16:15 ` Tom Tromey [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=87pm53snoq.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
/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).