🚀 go-pugleaf

In article <9002190631.AA19149@csvax.caltech.edu>
newton@CSVAX.CALTECH.EDU (Mike Newton) writes:

| Here are three gdb-3.4 comments/bugs/enhancements.  I know 3.5 is out,
| but I cant use that yet.  MANY thanks for gdb....
| 
| [1] A lot of my 'C' code is machine generated.  I write a file, 
| say 'foo.d' and a translator takes that into 'foo.c', putting
| 	# line 626 "list.d"
| this throws off gdb considerably.  (this may really be a 'gcc' bug...??)

This type of thing does not work when COFF debug information is kept,
since COFF only allows one 1 filename per object module, and the line
numbers within the function must be greater than or equal to the line
number of the first line of the function (which bites inlining).
Since you mentioned DG later in the document, I assume that is what
the problem is.

When I worked at Data General, I maintained that the "C" in COFF meant
crippled, and not common, mostly because of the limitations of the
debug format.
--
Michael Meissner	email: meissner@osf.org		phone: 617-621-8861
Open Software Foundation, 11 Cambridge Center, Cambridge, MA

Catproof is an oxymoron, Childproof is nearly so