public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/58123] New: [4.8 Regression] debug line not tracked for last autovariable dtor Date: Sun, 11 Aug 2013 11:16:00 -0000 [thread overview] Message-ID: <bug-58123-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58123 Bug ID: 58123 Summary: [4.8 Regression] debug line not tracked for last autovariable dtor Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: jan.kratochvil at redhat dot com Target: x86_64-unknown-linux-gnu PASS: g++ (GCC) 4.7.3 20130221 (prerelease) - it did not generate separate line info for destructors at all FAIL: g++ (GCC) 4.8.2 20130811 (prerelease) FAIL: g++ (GCC) 4.9.0 20130811 (experimental) class C { public: C() {} ~C() {} int m() { return 0; } }; /* 7 */ int main() { /* 8 */ C a; /* 9 */ C b; /* 10 */ C c; /* 11 */ return a.m() + b.m() + c.m(); /* 12 */ } ---------------------------------------------------------------------------- g++-4.7: (gdb) start 8 /* 8 */ C a; (gdb) next 9 /* 9 */ C b; (gdb) next 10 /* 10 */ C c; (gdb) next 11 /* 11 */ return a.m() + b.m() + c.m(); (gdb) next 12 /* 12 */ } ---------------------------------------------------------------------------- g++-4.8: each destructor has its own .debug_line entry: (gdb) start 8 /* 8 */ C a; (gdb) next 9 /* 9 */ C b; (gdb) next 10 /* 10 */ C c; (gdb) next 11 /* 11 */ return a.m() + b.m() + c.m(); (gdb) next 10 /* 10 */ C c; (gdb) next 9 /* 9 */ C b; (gdb) next ################## Missing: /* 8 */ C a; 11 /* 11 */ return a.m() + b.m() + c.m(); (gdb) next 12 /* 12 */ } except for the last one: /home/jkratoch/t/example2.C:10 4005f7: 48 8d 45 ed lea -0x13(%rbp),%rax 4005fb: 48 89 c7 mov %rax,%rdi 4005fe: e8 2b 00 00 00 callq 40062e <C::~C()> /home/jkratoch/t/example2.C:9 400603: 48 8d 45 ee lea -0x12(%rbp),%rax 400607: 48 89 c7 mov %rax,%rdi 40060a: e8 1f 00 00 00 callq 40062e <C::~C()> /home/jkratoch/t/example2.C:11 ############################^^ here should be :8 40060f: 48 8d 45 ef lea -0x11(%rbp),%rax 400613: 48 89 c7 mov %rax,%rdi 400616: e8 13 00 00 00 callq 40062e <C::~C()> ############################ Missing debug line for :11 or :12 here: 40061b: 89 d8 mov %ebx,%eax /home/jkratoch/t/example2.C:12 40061d: 48 83 c4 18 add $0x18,%rsp 400621: 5b pop %rbx 400622: 5d pop %rbp 400623: c3 retq Downstream user bugreport: https://bugzilla.redhat.com/show_bug.cgi?id=995804
next reply other threads:[~2013-08-11 11:16 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-11 11:16 jan.kratochvil at redhat dot com [this message] 2013-08-16 13:49 ` [Bug debug/58123] [4.8/4.9 " jakub at gcc dot gnu.org 2013-10-16 9:50 ` jakub at gcc dot gnu.org 2013-10-28 13:18 ` asmwarrior at gmail dot com 2013-11-21 14:24 ` rguenth at gcc dot gnu.org 2014-05-22 9:07 ` [Bug debug/58123] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:28 ` [Bug debug/58123] [4.8/4.9/5 " jakub at gcc dot gnu.org 2015-02-18 17:57 ` aldyh at gcc dot gnu.org 2015-02-18 21:13 ` aldyh at gcc dot gnu.org 2015-02-18 21:41 ` jan.kratochvil at redhat dot com 2015-02-19 17:35 ` aldyh at gcc dot gnu.org 2015-02-20 5:00 ` asmwarrior at gmail dot com 2015-02-21 1:01 ` aldyh at gcc dot gnu.org 2015-02-21 2:57 ` aldyh at gcc dot gnu.org 2021-04-14 0:20 ` cvs-commit at gcc dot gnu.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-58123-4@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: 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).