From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>
Cc: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb: add gdb_bfd_all_sections for range-based iteration
Date: Mon, 24 Aug 2020 17:30:53 -0400 [thread overview]
Message-ID: <de634927-1d5a-5c3e-2f79-5389adef6d62@polymtl.ca> (raw)
In-Reply-To: <875z97bw3p.fsf@tromey.com>
On 2020-08-24 4:57 p.m., Tom Tromey wrote:
>>> I also did this kind of thing -- I have some patches to remove many uses
>>> of bfd_map_over_sections, though not all of them, since some seem hard
>>> to test.
>
> Simon> What approach did you take?
>
> Almost exactly identical to yours -- I named the adapter
> "gdb_bfd_sections". I can resurrect some of my patches after yours
> lands.
>
> Tom
>
I modeled the "gdb_bfd_all_sections" on "all_threads" and "all_inferiors". But honestly
the "all" sounds superfluous now that I re-read it.
I'll push the patch with "all" removed from the name.
Thanks!
Simon
next prev parent reply other threads:[~2020-08-24 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 19:43 Simon Marchi
2020-08-24 20:31 ` Tom Tromey
2020-08-24 20:34 ` Simon Marchi
2020-08-24 20:57 ` Tom Tromey
2020-08-24 21:30 ` Simon Marchi [this message]
2020-08-27 12:59 ` 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=de634927-1d5a-5c3e-2f79-5389adef6d62@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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