Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] Make index reading functions more modular
Date: Wed, 25 Jul 2018 16:51:00 -0000	[thread overview]
Message-ID: <87muuf1cqi.fsf@tromey.com> (raw)
In-Reply-To: <1531173351-6351-2-git-send-email-simon.marchi@ericsson.com>	(Simon Marchi's message of "Mon, 9 Jul 2018 17:55:49 -0400")

>>>>> "Simon" == Simon Marchi <simon.marchi@ericsson.com> writes:

Simon> The read_gdb_index_from_section and read_debug_names_from_section
Simon> functions read the index content, as their names state, from sections of
Simon> object files.  A following patch will make it possible to read index
Simon> content from standalone files.

Simon> This patch therefore decouples the code that reads the index content
Simon> from the code that processes that content.  Functions
Simon> dwarf2_read_gdb_index and dwarf2_read_debug_names receive callbacks that
Simon> are responsible for providing the index contents (for both the main file
Simon> and the potential dwz file).

I think this looks reasonable.  (I was hoping there would be some way to
do it without callbacks, but I didn't see a good approach to that, and
I'd guess you didn't either.)

Tom


  reply	other threads:[~2018-07-25 16:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-09 21:56 [PATCH 0/3] Add a DWARF index cache Simon Marchi
2018-07-09 21:56 ` [PATCH 1/3] Make index reading functions more modular Simon Marchi
2018-07-25 16:51   ` Tom Tromey [this message]
2018-07-09 21:56 ` [PATCH 2/3] Introduce scoped_mmapped_file Simon Marchi
2018-07-24  2:18   ` Tom Tromey
2018-07-24 12:31     ` Simon Marchi
2018-07-09 21:57 ` [PATCH 3/3] Add DWARF index cache Simon Marchi
2018-07-17 19:48   ` Tom Tromey
2018-07-17 20:48     ` Simon Marchi
2018-07-18 18:20       ` Tom Tromey
2018-07-25 18:48   ` Tom Tromey
2018-07-25 20:20     ` Simon Marchi
2018-07-26 12:38     ` 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=87muuf1cqi.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.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