public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/40596] New: [4.5 regression] Bad debug info for local variables on i386. Date: Mon, 29 Jun 2009 21:02:00 -0000 [thread overview] Message-ID: <bug-40596-17355@http.gcc.gnu.org/bugzilla/> (raw) The test case from bug 40012 still fails in current mainline @149059 in 32-bit mode: --- cut --- struct list_s { struct list_s* next; }; typedef struct list_s list; void f1(void*, list*); int f0(void* a, void* b, void* c, list* d) { list* problem; for(problem = d; problem; problem = problem->next) { int variable = 0; f1(c, problem); } return (0); } int main() { list a3 = { 0 }; f0(0, 0, 0, &a3); return 0; } void f1(void*a, list*b) { } --- cut --- gcc-svn-install-149059/bin/gcc -g gcc-pr40012-test.c -m32 gdb -q a.out (gdb) b main Breakpoint 1 at 0x80483d9: file gcc-pr40012-test.c, line 24. (gdb) r Breakpoint 1, main () at gcc-pr40012-test.c:24 24 list a3 = { 0 }; (gdb) n 25 f0(0, 0, 0, &a3); (gdb) p &a3 $1 = (list *) 0xffffccb4 (gdb) s f0 (a=0x0, b=0x0, c=0x0, d=0xffffcc8c) at gcc-pr40012-test.c:15 15 for(problem = d; problem; problem = problem->next) { Note mismatch between where GDB thinks &a3 is and the actual address. [AFAICT, this is currently causing 300+ failures in the GDB test suite.] -- Summary: [4.5 regression] Bad debug info for local variables on i386. Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ppluzhnikov at google dot com GCC build triplet: x86_64-unknown-linux-gnu GCC host triplet: x86_64-unknown-linux-gnu GCC target triplet: x86_64-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40596
next reply other threads:[~2009-06-29 21:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-29 21:02 ppluzhnikov at google dot com [this message] 2009-06-29 21:51 ` [Bug debug/40596] " hjl dot tools at gmail dot com 2009-06-29 21:54 ` hjl dot tools at gmail dot com 2009-06-29 22:36 ` ppluzhnikov at google dot com 2009-06-29 23:44 ` jakub at gcc dot gnu dot org 2009-07-02 11:31 ` jakub at gcc dot gnu dot org 2009-07-04 17:19 ` jakub at gcc dot gnu dot org 2009-07-15 7:27 ` steven at gcc dot gnu dot org 2009-07-29 22:49 ` jsm28 at gcc dot gnu dot org 2009-07-29 22:51 ` ppluzhnikov at google dot com
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-40596-17355@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).