public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "deuling at de dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/35615] Debug information for .debug_loc section incorrect Date: Mon, 17 Mar 2008 19:29:00 -0000 [thread overview] Message-ID: <20080317192824.13589.qmail@sourceware.org> (raw) In-Reply-To: <bug-35615-15932@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from deuling at de dot ibm dot com 2008-03-17 19:28 ------- Hi Andrew, attached is my little test program I use. The error is seen both on x86 and PowerPC: * i686 i686 i386 GNU/Linux * ppc64 ppc64 ppc64 GNU/Linux following versions of binutils: x86: binutils-2.17.50.0.6-5.el5 PowerPC: binutils-2.17.50.0.12-4 objdump -W says: objdump: Error: Location lists in .debug_info section aren't in ascending order! Contents of the .debug_loc section: Offset Begin End Expression 00000000 080485b4 080485b5 (DW_OP_breg4: 4) 00000000 080485b5 080485b7 (DW_OP_breg4: 8) 00000000 080485b7 0804868b (DW_OP_breg5: 8) 00000000 <End of list> 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. As seen in comment #1 readelf also gives that error. AFAIK readelf does not use BFD library as GDB and objdump do so I believe this is not an error in BFD library. I use GDB's current head. I also tried gdb-6.5-25.el5_1.1 and it also occurs. Regards, Markus Deuling -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35615
next prev parent reply other threads:[~2008-03-17 19:29 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-03-17 13:58 [Bug fortran/35615] New: " deuling at de dot ibm dot com 2008-03-17 16:49 ` [Bug debug/35615] " pinskia at gcc dot gnu dot org 2008-03-17 19:21 ` deuling at de dot ibm dot com 2008-03-17 19:29 ` deuling at de dot ibm dot com [this message] 2008-03-17 23:32 ` wilson at tuliptree dot org 2008-03-18 13:44 ` deuling at de dot ibm dot com 2008-03-18 16:53 ` deuling at de dot ibm dot com 2008-03-19 0:55 ` amodra at bigpond dot net dot au 2008-03-19 1:18 ` amodra at bigpond dot net dot au 2008-03-19 8:48 ` deuling at de dot ibm dot com 2008-03-19 8:49 ` deuling at de dot ibm dot com 2008-03-20 6:56 ` wilson at tuliptree dot org 2008-03-20 13:02 ` deuling at de dot ibm dot com 2008-03-21 19:31 ` drow at gcc dot gnu dot org
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=20080317192824.13589.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).