public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "aegges at web dot de" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/16470] New: Crash when inspecting STL containers with GDB pretty print Date: Mon, 20 Jan 2014 12:51:00 -0000 [thread overview] Message-ID: <bug-16470-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16470 Bug ID: 16470 Summary: Crash when inspecting STL containers with GDB pretty print Product: gdb Version: 7.6 Status: NEW Severity: critical Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: aegges at web dot de I have the following source code: #include <list> using namespace std; int main() { list<int> x; list<int> y; x.push_back(1); y.push_back(2); return 0; } I installed the python pretty printers for STL from the GNU website and load them in my .gdbinit. GDB crashes when I inspect the STL list. To reproduce from the command line: gdb -i mi -nx -enable-pretty-printing -gdb-set print object on source /home/amueller/.gdbinit -file-exec-and-symbols --thread-group i1 /home/amueller/testing/test -break-insert --thread-group i1 -f /home/amueller/testing/test.cpp:12 -break-insert --thread-group i1 -t -f main -exec-run --thread-group i1 -var-create --thread-group i1 - * x -var-create --thread 1 --frame 0 - * x -var-list-children var2 -exec-continue --thread 1 -var-update 1 var2 The bug was initially reported for Eclipse but also occurs using the command line gdb. See http://www.eclipse.org/forums/index.php/t/636361/ -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-01-20 12:51 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-20 12:51 aegges at web dot de [this message] 2014-01-21 8:41 ` [Bug python/16470] " marc.khouzam at ericsson dot com 2014-01-26 8:12 ` xhpohanka at gmail dot com 2014-01-26 9:28 ` qiyao at gcc dot gnu.org 2014-01-27 7:21 ` xhpohanka at gmail dot com 2014-01-27 8:31 ` qiyao at gcc dot gnu.org 2014-01-27 12:14 ` xhpohanka at gmail dot com 2021-09-15 7:02 ` beaux_monde at tut dot by 2022-06-07 15:36 ` tromey at sourceware dot org 2023-08-31 19:21 ` tromey at sourceware 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-16470-4717@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).