public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arnez at linux dot vnet.ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/54887] New: gdb test case failure with mi-var-rtti Date: Wed, 10 Oct 2012 14:39:00 -0000 [thread overview] Message-ID: <bug-54887-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54887 Bug #: 54887 Summary: gdb test case failure with mi-var-rtti Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: debug AssignedTo: unassigned@gcc.gnu.org ReportedBy: arnez@linux.vnet.ibm.com Current upstream gcc causes a regression with the gdb test case mi-var-rtti.exp: FAIL: gdb.mi/mi-var-rtti.exp: create varobj for ptr (without RTTI) in use_rtti_for_ptr ... Here's a link to the C++ source: http://sourceware.org/cgi-bin/cvsweb.cgi/~checkout~/src/gdb/testsuite/gdb.mi/mi-var-rtti.cc?rev=1.1&cvsroot=src The test case sets a breakpoint in use_rtti_for_ptr_test() on the last variable declaration ('constPtrConst', line 37) and then advances with 'next' to the return statement. There it tries to access the variable 'ptr', but the 'next' already carried us into the epilogue beyond that variable's lexical block. This is because the line number information now places the return statement _after_ everything else, even after the destructor call for 'd'. I've verified the failure on x86_64 and s390x. The regression was introduced by: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=191338
next reply other threads:[~2012-10-10 14:39 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-10 14:39 arnez at linux dot vnet.ibm.com [this message] 2012-10-10 15:48 ` [Bug debug/54887] " dehao at gcc dot gnu.org 2012-10-10 17:15 ` arnez at linux dot vnet.ibm.com 2012-10-10 17:57 ` dehao at gcc dot gnu.org 2012-10-11 8:29 ` arnez at linux dot vnet.ibm.com 2012-10-24 17:52 ` arnez at linux dot vnet.ibm.com 2012-10-24 17:56 ` dehao at gcc dot gnu.org 2012-10-24 21:25 ` dehao 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-54887-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).