From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>,
Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [gdb/symtab] Add set/show always-read-ctf on/off
Date: Sat, 25 Feb 2023 05:34:35 -0700 [thread overview]
Message-ID: <875ybp2aas.fsf@tromey.com> (raw)
In-Reply-To: <cee02f2d-55df-fa5a-574c-428cba7ad7a0@suse.de> (Tom de Vries's message of "Sat, 25 Feb 2023 09:42:35 +0100")
Tom> Hmm, I'm starting to wonder now, perhaps a way to cover both scenarios
Tom> (the one described above and the non-overlapping dwarf+ctf one I'm
Tom> trying to fix) is to check where the dwarf came from:
Tom> - if the dwarf resides in the same object file as the ctf, read both
Tom> - if the dwarf doesn't come from the same object file (so, it comes from
Tom> a debug info package or debug info server), skip the ctf
Tom> I suppose that'll work, but even so I still think it makes sense to
Tom> make it configurable. For instance, the added test-case in
Tom> combination with target board cc-with-gnu-debuglink will need
Tom> convincing to read both ctf an dwarf, even if the dwarf has been split
Tom> off.
Tom> WDYT?
I think your original approach is fine as well, and I'd hate to make it
more complicated for you.
Tom
next prev parent reply other threads:[~2023-02-25 12:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 12:35 Tom de Vries
2023-02-24 19:33 ` Tom Tromey
2023-02-25 8:42 ` Tom de Vries
2023-02-25 12:34 ` Tom Tromey [this message]
2023-02-26 8:25 ` Tom de Vries
2023-03-02 1:56 ` Tom Tromey
2023-03-02 7:18 ` Tom de Vries
2023-03-02 9:38 ` Eli Zaretskii
2023-03-02 9:58 ` Tom de Vries
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=875ybp2aas.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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).