dbx can only interpret debug info in some files

[GoogleCodeExporter]

also, sometime after r180, dbx is not happy with the debug info we produce
anymore: no more type info, no more line number info. could have been
caused by tmp fix for fred's issues on x86_64. need to fix this asap.

Original issue reported on code.google.com by [email protected] on 9 Dec 2008 at 1:10

[GoogleCodeExporter]

actually, this is not a regression. the behaviour was like this the whole time, 
I
just did not notice it. with some sources, line numbers work. with some type 
info
works. with some both work. with many, none work.

all possible COFF flags are the same in all cases.

COFF debugging info seems the same (and valid) in all cases.

Original comment by [email protected] on 9 Dec 2008 at 3:16

• Added labels: binutils, gcc-debug

[GoogleCodeExporter]

also, objdump -g presents nice debug info in all cases.

whether dbx recognizes (some part of) debug info is a function of the source 
code.
for some sources it works, for some it doesn't. no obvious reason.

Original comment by [email protected] on 9 Dec 2008 at 4:28

• Changed title: dbx can only interpret debug info in some files
• Added labels: Priority-Critical
• Removed labels: Priority-High

[GoogleCodeExporter]

Original comment by [email protected] on 10 Dec 2008 at 9:27

• Added labels: Priority-Low
• Removed labels: Priority-Critical