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 21:22:00 -0000	[thread overview]
Message-ID: <m3aaxu8op8.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20091207203323.GA29440@caradoc.them.org> (Daniel Jacobowitz's 	message of "Mon, 7 Dec 2009 15:33:23 -0500")

>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:

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

Daniel> then you just give GDB the ELF file.  I've never seen a reference from
Daniel> a non-ELF executable to ELF debug info.

Thanks.  I think that settles it.

Tom


  reply	other threads:[~2009-12-07 21:22 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
2009-12-07 20:33       ` Daniel Jacobowitz
2009-12-07 21:22         ` Tom Tromey [this message]
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=m3aaxu8op8.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