🚀 go-pugleaf

In article <9208261514.AA24807@turing.think.com!> randys@think.com (Randall Smith) writes:
!>    In the function define_symbol in gdb-4.6 read the following words:

[ code containing "abort() if unexpected characters appear in the symbol name]

!>    I question the wisdom of calling abort from within define_symbol.
!>  Specifically, you may be (I am) debugging a mixed C/some other random
!>  language program and wish to use gdb on it.  That other random language
!>  may have added extensions to the dbx symbol format that gdb doesn't
!>  understand, but that do not render gdb useless in debugging that
!>  language.

Could this and similar practices have something to do with why gdb aborts
when debugging acc (Sun's bundled compiler) code, because it does not
recognize Sun's (undocumented) extensions?  There should be some less
drastic response to "I don't understand this symbol information" than
"kablooie".

(I recognize that this can be difficult to do, since there is sometimes
a re-synchronization step required).




--
Joe Buck	jbuck@ohm.berkeley.edu