Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!sdd.hp.com!samsung!xylogics!world!esegue!compilers-sender From: title@Think.COM (Richard Title) Newsgroups: comp.compilers Subject: Re: '.stabs' info requested Keywords: C, debug Message-ID: <1990Jun6.150120.1572@esegue.segue.boston.ma.us> Date: 6 Jun 90 15:01:20 GMT References: <1990Jun5.173819.2970@esegue.segue.boston.ma.us> Sender: compilers-sender@esegue.segue.boston.ma.us Reply-To: title@Think.COM (Richard Title) Organization: Thinking Machines Corporation, Cambridge MA, USA Lines: 27 Approved: compilers@esegue.segue.boston.ma.us In article <1990Jun5.173819.2970@esegue.segue.boston.ma.us> Andre Marien 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 -- Send compilers articles to compilers@esegue.segue.boston.ma.us {spdcc | ima | lotus}!esegue. Meta-mail to compilers-request@esegue. Please send responses to the author of the message, not the poster.