|'.stabs' info requested bimandre@BLEKUL60.BITNET (Andre Marien) (1990-06-05)|
|Re: '.stabs' info requested email@example.com (1990-06-06)|
|Re: '.stabs' info requested title@Think.COM (1990-06-06)|
|Re: '.stabs' info requested firstname.lastname@example.org (1990-06-07)|
|Re: '.stabs' info requested email@example.com (1990-06-07)|
|Re: '.stabs' info requested firstname.lastname@example.org (1990-06-14)|
|From:||email@example.com (David Keppel)|
|Date:||Thu, 7 Jun 90 04:08:10 GMT|
|Organization:||University of Washington, Computer Science, Seattle|
title@Think.COM (Richard Title) writes:
>[dbx .stabs documentation: `stabstring.c']
One piece of information that you won't find in the dbx documentation:
some perfectly legal .stabs entries cause popular (e.g., BSD VAX)
assemblers to barf with a message like ``illegal .stabs value''.
The problem is severe enough that at least for a while, GNU C++ had a
compiler compile-time flag ``FASCIST_ASSEMBLER''. The first time that I
built a version of GNU C++ that had this flag, I missed the fact that I
needed to set the flag, and assembly failed as a result. I took the
problem to one of the authors of BSD `as', and he agreed that it was a
bug in `as'.
One moral of the story is ``do it the right way, have a flag for broken
;-D on ( Undebugger ) Pardo
Return to the
Search the comp.compilers archives again.