Related articles |
---|
'.stabs' info requested bimandre@BLEKUL60.BITNET (Andre Marien) (1990-06-05) |
Re: '.stabs' info requested bothner@cs.wisc.edu (1990-06-06) |
Re: '.stabs' info requested title@Think.COM (1990-06-06) |
Re: '.stabs' info requested pardo@cs.washington.edu (1990-06-07) |
Re: '.stabs' info requested dupuy@hudson.cs.columbia.edu (1990-06-07) |
Re: '.stabs' info requested meissner@osf.org (1990-06-14) |
Newsgroups: | comp.compilers |
From: | title@Think.COM (Richard Title) |
References: | <1990Jun5.173819.2970@esegue.segue.boston.ma.us> |
Date: | Wed, 6 Jun 90 15:01:20 GMT |
Organization: | Thinking Machines Corporation, Cambridge MA, USA |
Keywords: | C, debug |
In article <1990Jun5.173819.2970@esegue.segue.boston.ma.us> Andre Marien <bimandre@BLEKUL60.BITNET> writes:
>[is there documentation on the .stabs symbols generated by cc -g]
I couldn't find any external documentation of the stabs either so I resorted
to looking at the dbx sources. The Berkeley dbx sources are freely
available; the file that processes stabs is "stabstring.c". I'll mail
you a copy of that file. It takes a little work but you can deduce everything
from the source.
As far as I can tell, ULTRIX dbx is pretty close to Berkeley dbx so
looking at Berkeley dbx sources will probably suffice to answer questions
about what ULTRIX dbx accepts.
On the other hand, Sun has made a number of dbx extensions, including
some extensions to the stabs. You'll probably have to talk to Sun to
get more info.
I don't know anything about Sequent's dbx.
If anyone has stab documentation other than the dbx sources, I'd be
interested too.
- Rich
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.