public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "daniel.lopez999 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/13669] Infinite recursion in cp_print_value_fields Date: Thu, 05 Mar 2015 03:11:00 -0000 [thread overview] Message-ID: <bug-13669-4717-9uBWxnIobi@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13669-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=13669 --- Comment #12 from Daniel Lopez <daniel.lopez999 at gmail dot com> --- I've got a reproducible example of this. Compile attached "Daniel - test program" with g++ -std=c++0x -g main.cpp -omain Start gdb gdb main Put a breakpoint on line 53 return ref; // <-- stop here, then run 'finish' Then run 'finish' as the comment says. After a second or so gdb segfaults. An example of my stack trace is in "Daniel - debug session including backtrace". It's stuck in the same two functions that Orgad mentioned. I'm working with gdb 7.9 on Arch Linux, and 7.7 in an Ubuntu VM. (Just as an aside, would anyone have an idea why in the Ubuntu VM this simply causes gdb to exit back to the shell with "Segmentation fault (core dumped)" and I can try again and so on, whereas on the Arch machine it hangs leaving the gdb process in uninterruptible sleep state - preventing new gdb sessions from running - and I can't figure out how to get rid of it except restarting the machine?) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-03-05 3:06 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-07 12:11 [Bug gdb/13669] New: " orgads at gmail dot com 2012-02-07 12:13 ` [Bug gdb/13669] " orgads at gmail dot com 2012-02-07 12:55 ` andre.poenitz at nokia dot com 2012-02-07 16:54 ` tromey at redhat dot com 2012-02-07 20:43 ` orgads at gmail dot com 2012-02-07 21:24 ` tromey at redhat dot com 2012-02-08 10:29 ` orgads at gmail dot com 2012-02-08 11:14 ` orgads at gmail dot com 2012-02-08 18:02 ` tromey at redhat dot com 2012-02-09 8:03 ` orgads at gmail dot com 2012-02-09 8:07 ` orgads at gmail dot com 2014-09-12 23:07 ` sergiodj at redhat dot com 2015-03-05 2:54 ` daniel.lopez999 at gmail dot com 2015-03-05 3:06 ` daniel.lopez999 at gmail dot com 2015-03-05 3:11 ` daniel.lopez999 at gmail dot com [this message] 2015-03-05 20:43 ` daniel.lopez999 at gmail 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-13669-4717-9uBWxnIobi@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).