From: Ian Lance Taylor <ian@wasabisystems.com>
To: Bob Rossi <bob@brasko.net>
Cc: gdb@sources.redhat.com
Subject: Re: Executable's debug format
Date: Fri, 13 Feb 2004 03:03:00 -0000 [thread overview]
Message-ID: <m34qtvr89l.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20040213005432.GA4476@white>
Bob Rossi <bob@brasko.net> writes:
> Is there a way to find out what debug format the debugging info in the
> executable is in?
Yes, but I don't know of a trivial way.
Run objdump -h to see the sections.
If the program has a .debug it is using DWARF 1.
If the program has a .debug_info it is using DWARF 2.
If the program has .stab and .stabstr sections it is using stabs
debugging information.
There are many other possibilities, though those are the most common
these days.
> 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.
Ian
next prev parent reply other threads:[~2004-02-13 3:03 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 [this message]
2004-02-16 3:32 ` Daniel Jacobowitz
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=m34qtvr89l.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=bob@brasko.net \
--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