From: Mike Haertel <mike@ducky.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] software ports
Date: Sat, 22 Jul 2000 10:33:43 -0700 [thread overview]
Message-ID: <200007221733.KAA88238@ducky.net> (raw)
In-Reply-To: <200007221537.LAA00818@cse.psu.edu>
In comp.os.plan9, you wrote:
>Without that, I'm sure we'll just hit a debugging wall.
>Anyone know what gdb expects?
With Elf binaries, gdb can work with two different kinds of debugging
symbols: Berkeley dbx-style "stabs" (which gdb expects to find in
Elf sections named ".stab" and ".stabstr"), or AT&T-style DWARF
debugging symbols, which have a different set of ELF section names.
ftp://tsx-11.mit.edu/pub/linux/packages/GCC/ELF.doc.tar.gz
(describes basic Elf file format, but not debugging symbols)
There is some documentation for the DWARF2 debugging format
in ftp://sgigate.sgi.com/pub/dwarf.
The "stabs" debugging format is described in the dbx(5) man page
under 4.3BSD. Unfortunately, this documentation does not seem to
exist in any of the recent free *BSD's; this is a valuable man page
and I don't know what became of it. If you have a printed copy of
the old Usenix 4.3BSD manuals you can find it there (that's what I
have), or if you have a 4.3bsd tape sitting around you'll find it
there. Anyway the stabs format has probably evolved somewhat since
the 4.3bsd man page was written, moreover I think gdb has its own
slightly idiosyncratic variation that fixes some problems with the
original dbx format. So if you want a well-documented format you're
probably better off with DWARF.
next prev parent reply other threads:[~2000-07-22 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-22 15:36 Russ Cox
2000-07-22 17:33 ` Mike Haertel [this message]
2000-07-25 8:41 ` Michael Joosten
-- strict thread matches above, loose matches on Subject: below --
2000-07-22 19:19 pip
2000-07-22 18:56 forsyth
2000-07-15 20:56 Russ Cox
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=200007221733.KAA88238@ducky.net \
--to=mike@ducky.net \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).