From: Daniel Jacobowitz <drow@false.org>
To: Ian Lance Taylor <ian@wasabisystems.com>
Cc: Bob Rossi <bob@brasko.net>, gdb@sources.redhat.com
Subject: Re: Executable's debug format
Date: Mon, 16 Feb 2004 03:32:00 -0000 [thread overview]
Message-ID: <20040216033225.GC2685@nevyn.them.org> (raw)
In-Reply-To: <m34qtvr89l.fsf@gossamer.airs.com>
On Thu, Feb 12, 2004 at 10:03:02PM -0500, Ian Lance Taylor wrote:
> > Or is it more complicated? Can a single executable be composed of object
> > files which each have there debugging info in a different format?
>
> Yes, that is possible, though very unusual.
It happens pretty frequently on fairly-but-not-excessively recent
GNU/Linux systems. Some system library will be built against crt*
objects built before GCC's default changed to -gstabs+ and then user
code will use a more recent GCC that prefers -gdwarf-2. In fact, GDB
has had some interesting bugs guessing the address ranges of psymtabs
in such cases.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-16 3:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 0:54 Bob Rossi
2004-02-13 3:03 ` Ian Lance Taylor
2004-02-16 3:32 ` Daniel Jacobowitz [this message]
2004-02-13 9:11 ` Eli Zaretskii
2004-02-13 14:48 ` Kris Warkentin
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=20040216033225.GC2685@nevyn.them.org \
--to=drow@false.org \
--cc=bob@brasko.net \
--cc=gdb@sources.redhat.com \
--cc=ian@wasabisystems.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