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: Mon, 07 Dec 2009 20:13:00 -0000	[thread overview]
Message-ID: <m3638ia6ge.fsf@fleche.redhat.com> (raw)
In-Reply-To: <2CC5EFB8-A1BC-4025-9136-E8FA344B2C04@adacore.com> (Tristan 	Gingold's message of "Mon, 7 Dec 2009 11:50:23 +0100")

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

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

Tristan> I was hesitant to do that given that only ELF and some COFF
Tristan> support .gnu_debuglink.

I see.

After I sent my note, I wondered about folks doing something like
building an ELF executable, objcopy'ing it to some other format for
running it, but continuing to use the ELF for debugging.  Do people do
that?

If so then that would be a situation where the primary objfile could be
of any type, but still have separate debug info.

If not, then I agree your change is safe.

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> To be honest, I reserved this move for a following patch.  Do
Tristan> you prefer I resubmit this patch with this change ?

If it is coming later, then I don't mind, do whatever is most
convenient.

Tom


  reply	other threads:[~2009-12-07 20:13 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
2009-12-07 10:50   ` Tristan Gingold
2009-12-07 20:13     ` Tom Tromey [this message]
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=m3638ia6ge.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