Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Make sym_read routines handle separate debug files
Date: Fri, 04 Dec 2009 18:02:00 -0000	[thread overview]
Message-ID: <m38wdifwj1.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20091204124838.GA5764@ulanbator.act-europe.fr> (Tristan 	Gingold's message of "Fri, 4 Dec 2009 13:48:38 +0100")

>>>>> "Tristan" == Tristan Gingold <gingold@adacore.com> writes:

Tristan> Each object file reader is now responsible to read separate
Tristan> debug files as they are object file dependant.  Of course, in
Tristan> the case of gnu .debuglink a common subprogram is used.

You updated coffread and elfread, but the existing code in gdb does not
depend on the format.  So it seems to me that any other code defining
sym_fns will regress.  That is, dbxread, mipsread, somread, and
xcoffread (I omitted machoread since I presume your later patch fixes
that up).

Could we not just keep the existing logic as a format-independent
fallback?

Or am I mistaken about something?  Maybe it is impossible for those
formats to have separate debug files?  I know nothing of the details,
I'm afraid.

Tristan> +      debugfile = find_separate_debug_file_by_buildid (objfile);

If this is only meaningful for ELF, as it seems to be, then it seems we
might as well put it in elfread.c.

Tristan> +/* Add BFD as a separate debug file for OBJFILE.  */
Tristan> +
Tristan> +void
Tristan> +symbol_file_add_separate (bfd *bfd, int symfile_flags, struct objfile *objfile)
Tristan> +{
Tristan> +  objfile->separate_debug_objfile =

I'm wondering if this should have a sanity check and call internal_error
if the separate debug objfile is already set.

Tristan> @@ -2320,204 +2314,217 @@ reread_symbols (void)
[...]
Tristan> +	  /* The "mainline" parameter is a hideous hack; I think leaving it
Tristan> +	     zero is OK since dbxread.c also does what it needs to do if
Tristan> +	     objfile->global_psymbols.size is 0.  */

Normally I wouldn't ask for changes in a simple reindentation (and there
are other stale comments here that I didn't single out), but this
particular comment seems relevant to the overall change.  I suggest just
removing it, but rewording would be ok too.

Tom


  reply	other threads:[~2009-12-04 18:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-04 12:48 Tristan Gingold
2009-12-04 18:02 ` Tom Tromey [this message]
2009-12-07 10:50   ` Tristan Gingold
2009-12-07 20:13     ` Tom Tromey
2009-12-07 20:33       ` Daniel Jacobowitz
2009-12-07 21:22         ` Tom Tromey
2009-12-08 10:57       ` Tristan Gingold
2009-12-08 16:54         ` Tom Tromey
2009-12-09 13:45           ` Tristan Gingold

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=m38wdifwj1.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gingold@adacore.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