This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Bug in Fortran: DW_AT_name


Hi,

I try to debug a Fortan binary produced by gcc 4.3. I get:

Breakpoint 1, MAIN__ () at :1
1       : No such file or directory.
       in 
(gdb) info frame
Stack level 0, frame at 0xbfcec3e0:
eip = 0x80485bd in MAIN__ (:1); saved eip 0x80486c9

objdump is able to read the DW_AT_name

<0><b>: Abbrev Number: 1 (DW_TAG_compile_unit)
    DW_AT_producer    : (indirect string, offset: 0x41): GNU F95 4.3.0­
    DW_AT_language    : 14­····(Fortran 95)
    DW_AT_name        : (indirect string, offset: 0x0): ./neg_array.F­·
    DW_AT_comp_dir    : (indirect string, offset: 0x1b): /home/deuling/fortran­

but shows following error:

objdump: Error: Location lists in .debug_info section aren't in ascending order!
objdump: Warning: There is an overlap [0x2c - 0xfffffffe] in .debug_loc section.
objdump: Warning: Offset 0xfffffffe is bigger than .debug_loc section size.
objdump: Warning: There is a hole [0xfffffffe - 0x2c] in .debug_loc section.

C-code works fine.

For my opinion this is a compiler bug in fortran. But as objdump is able to recognize DW_AT_name maybe GDB should, too? What do you think ?

--
 Markus Deuling
 GNU Toolchain for Linux on Cell BE
 deuling@de.ibm.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]