public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "ischdoepperdodrausse at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/15468] New: crash breakpoint.c:5940: internal-error: print_one_breakpoint_location Date: Wed, 15 May 2013 08:36:00 -0000 [thread overview] Message-ID: <bug-15468-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15468 Bug #: 15468 Summary: crash breakpoint.c:5940: internal-error: print_one_breakpoint_location Product: gdb Version: 7.6 Status: NEW Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned@sourceware.org ReportedBy: ischdoepperdodrausse@gmail.com Classification: Unclassified I use gdb in emacs (24.3, trunk) with GUD. Then I set a execption point through "catch throw". This works. Also, all is good if execption point is reached. But as soon as I try to print the catch point -> crash. When using M-x gud-gdb (with gdb --fullname) there is no automatic display of breakpoints. So crash occurs if I try to print the breakpoints excplictely. When using M-x gdb version of GUD with "gdb -i=mi ..." and have all frames displayed (threads, breakpoints, watches, ...) crash occurs directly after executing "catch throw". Please see transcript below: GNU gdb (GDB) 7.6 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Loaded STL pretty printers Loading ~/.gdb/pythonPegaPlan.py Loaded ~/.gdb/pythonPegaPlan.py Reading symbols from /users/q4de3tsy926/user3/heierma1/sniff/6.4/appl/fscp/fscp_gui/linux-gnu/fscp.exe...done. (gdb) catch throw Catchpoint 1 (throw) (gdb) r Starting program: /users/q4de3tsy926/user3/heierma1/sniff/6.4/appl/fscp/fscp_gui/linux-gnu/fscp.exe [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/tls/libthread_db.so.1". *** starting module PP FsCp (PP 6.4.3) linked on May 15 2013 at 02:14:19 on linux-gnu *** fscp.exe: initializing ... [New Thread 0x40200960 (LWP 21881)] [New Thread 0x40401960 (LWP 21882)] [New Thread 0x40602960 (LWP 21883)] Catchpoint 1 (exception thrown), __cxxabiv1::__cxa_throw (obj=0x89ad470, tinfo=0x2920e60 <typeinfo for EShapefileError>, dest=0x17f1fdc <EShapefileError::~EShapefileError()>) at /users/dxcoty/user1/markus/MAKE/gcc-4.1.2/libstdc++-v3/libsupc++/eh_throw.cc:64 64 /users/dxcutz/user1/heiner/MAKE/gcc-4.1.2/libstdc++-v3/libsupc++/eh_throw.cc: No such file or directory. (gdb) i b Num Type Disp Enb Address What 1 breakpoint keep y breakpoint.c:5940: internal-error: print_one_breakpoint_location: Assertion `b->loc == NULL || b->loc->next == NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y breakpoint.c:5940: internal-error: print_one_breakpoint_location: Assertion `b->loc == NULL || b->loc->next == NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Unable to dump core, use `ulimit -c unlimited' before executing GDB next time. Debugger exited abnormally with code 1 FYI: The bug is also referenced in the IMHO unrelated kde(velop) bug tracking system: https://bugs.kde.org/show_bug.cgi?id=316656 -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2013-05-15 8:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-15 8:36 ischdoepperdodrausse at gmail dot com [this message] 2013-05-15 17:25 ` [Bug c++/15468] " tromey at redhat dot com 2013-05-16 11:48 ` ischdoepperdodrausse at gmail dot com 2013-05-16 14:14 ` tromey at redhat dot com 2013-05-18 0:17 ` ischdoepperdodrausse at gmail dot com 2017-01-03 21:32 ` spencerbaugh 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-15468-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).