public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jan dot kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/40713] New: Overlapping .debug_ranges (C++)
Date: Fri, 10 Jul 2009 15:16:00 -0000 [thread overview]
Message-ID: <bug-40713-12292@http.gcc.gnu.org/bugzilla/> (raw)
class C {
C();
void f() {};
};
C::C() { f(); };
g++ -c -o cu-overlap.o cu-overlap.C -g -O0
readelf --debug-dump=Ranges cu-overlap.o
Contents of the .debug_ranges section:
Offset Begin End
00000000 0000000000000000 0000000000000034
00000000 0000000000000000 000000000000000a
00000000 0000000000000000 000000000000001a
00000000 000000000000001a 0000000000000034
00000000 <End of list>
Relocation section '.rela.debug_ranges' at offset 0x1560 contains 8 entries:
Offset Type Symbol's Value Symbol's Name + Addend
0000000000000000 R_X86_64_64 0000000000000000 .text + 0
0000000000000008 R_X86_64_64 0000000000000000 .text + 34
0000000000000010 R_X86_64_64 0000000000000000 .text._ZN1C1fEv + 0
0000000000000018 R_X86_64_64 0000000000000000 .text._ZN1C1fEv + a
0000000000000020 R_X86_64_64 0000000000000000 .text + 0
0000000000000028 R_X86_64_64 0000000000000000 .text + 1a
0000000000000030 R_X86_64_64 0000000000000000 .text + 1a
0000000000000038 R_X86_64_64 0000000000000000 .text + 34
DWARF3 2.17.3: Address range entries in a range list may not overlap.
Contents of the .debug_ranges section:
Offset Begin End
1st 00000000 0000000000000000 0000000000000034 - is from .Ltext0 .. .Letext0
2nd 00000000 0000000000000000 000000000000000a - NOT overlapping, COMDAT C::f()
3rd 00000000 0000000000000000 000000000000001a - is from first C::C() instance
4th 00000000 000000000000001a 0000000000000034 - is from second C::C() instance
1st overlaps with 3rd+4th.
--
Summary: Overlapping .debug_ranges (C++)
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jan dot kratochvil at redhat dot com
GCC target triplet: x86_64-unknown-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40713
next reply other threads:[~2009-07-10 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 15:16 jan dot kratochvil at redhat dot com [this message]
2009-07-10 18:28 ` [Bug debug/40713] " jakub at gcc dot gnu dot org
2009-07-10 19:34 ` jakub at gcc dot gnu dot org
2009-07-11 17:42 ` jakub at gcc dot gnu dot org
2010-05-24 11:13 ` jakub 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=bug-40713-12292@http.gcc.gnu.org/bugzilla/ \
--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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).