From: Daniel Jacobowitz <drow@false.org>
To: Brian Ford <ford@vss.fsi.com>
Cc: gdb@sources.redhat.com
Subject: Re: Are mixed debug formats in one exe supported?
Date: Wed, 24 Mar 2004 10:29:00 -0000 [thread overview]
Message-ID: <20040323234657.GA24923@nevyn.them.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0403231737350.17486@thing1-200>
On Tue, Mar 23, 2004 at 05:44:10PM -0600, Brian Ford wrote:
> On Tue, 23 Mar 2004, Brian Ford wrote:
> > I almost see why. Can someone please tell me why this comment above
> > elfstab_build_psymtabs is true for the DWARF part?
> >
> > This ELF file has already been processed to get its minimal symbols,
> > and any DWARF symbols that were in it.
> >
> > ie. What gaurantees that DWARF is processed before stabs? I can't see
> > that yet. If I can understand that, I think I can easily fix my problem.
> >
> > Thanks again.
> >
> Sorry to follow up my own post, but I'm now even more confused.
>
> >From what I can see, the order (for elf) is gauranteed to be ECOFF, stabs,
> DWARF2, DWARF, DWARF2 frame info. So, that comment just looks wrong. And, I
> still don't understand why it works on Linux.
The order shouldn't even matter at all. Neither the stabs nor dwarf
code will add the ELF minimal symbols, and then stabs will add some and
dwarf the others.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2004-03-23 23:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 22:40 Brian Ford
2004-03-23 22:42 ` Daniel Jacobowitz
2004-03-23 23:47 ` Brian Ford
2004-03-24 7:12 ` Brian Ford
2004-03-24 9:25 ` Brian Ford
2004-03-24 10:29 ` Daniel Jacobowitz [this message]
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=20040323234657.GA24923@nevyn.them.org \
--to=drow@false.org \
--cc=ford@vss.fsi.com \
--cc=gdb@sources.redhat.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