From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/breakpoints] Fix longjmp master breakpoint with separate debug info
Date: Thu, 28 Jan 2021 13:07:18 -0700 [thread overview]
Message-ID: <87eei44yh5.fsf@tromey.com> (raw)
In-Reply-To: <6a0c1c97-4acc-5a50-4ae3-3279e51493d9@suse.de> (Tom de Vries's message of "Thu, 28 Jan 2021 10:55:31 +0100")
Tom> [ BTW, I think separate_debug_iterator / separate_debug_range is a bit
Tom> of a misnomer, if it iterates over the parent obj first. It iterates
Tom> over all the objects that could contain debug information, also if
Tom> there's no separate debug info to begin with, f.i. if the parent object
Tom> is unstripped and contains all the debug info.
Tom> So perhaps debug_objfile_iterator / debug_objfile_range is more
Tom> appropriate ? ]
Yeah, now that you point it out, I agree that the current name seems a
bit off.
debug_objfile_* seems a little generic though.
What about maybe 'all_related_objfiles', the idea being that you pass in
an objfile and it iterates over all the "related" ones -- both it and
the separate debug files?
Tom
prev parent reply other threads:[~2021-01-28 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 14:31 Tom de Vries
2021-01-27 21:37 ` Tom Tromey
2021-01-28 9:55 ` Tom de Vries
2021-01-28 20:07 ` 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=87eei44yh5.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