Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Markus Deuling <deuling@de.ibm.com>
To: GDB discuss <gdb@sourceware.org>
Subject: Bug in Fortran: DW_AT_name
Date: Fri, 14 Mar 2008 08:28:00 -0000	[thread overview]
Message-ID: <47DA34D4.8090402@de.ibm.com> (raw)

Hi,

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

Breakpoint 1, MAIN__ () at \x01:1
1       \x01: No such file or directory.
        in \x01
(gdb) info frame
Stack level 0, frame at 0xbfcec3e0:
 eip = 0x80485bd in MAIN__ (\x01: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


             reply	other threads:[~2008-03-14  8:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14  8:28 Markus Deuling [this message]
2008-03-14  9:12 ` Markus Deuling
2008-03-18 21:16   ` Markus Deuling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47DA34D4.8090402@de.ibm.com \
    --to=deuling@de.ibm.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox