From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Correctly handle forward DIE references in scanner
Date: Mon, 15 May 2023 09:16:21 -0600 [thread overview]
Message-ID: <87wn19sjzu.fsf@tromey.com> (raw)
In-Reply-To: <877ct93b1m.fsf@tromey.com> (Tom Tromey's message of "Mon, 15 May 2023 08:48:53 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> I'm going check this in on master and gdb-13 now.
I noticed in the backport that the test doesn't really verify the
result, because 13 doesn't show the symbols in "maint print objfiles".
However, I don't think this is extremely important on this branch, so
I'm going ahead.
Tom
prev parent reply other threads:[~2023-05-15 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 22:10 Tom Tromey
2023-05-15 14:48 ` Tom Tromey
2023-05-15 15:16 ` 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=87wn19sjzu.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.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).