From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16237 invoked by alias); 15 May 2013 08:36:04 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 16215 invoked by uid 48); 15 May 2013 08:36:04 -0000 From: "ischdoepperdodrausse at gmail dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ischdoepperdodrausse at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 X-SW-Source: 2013-q2/txt/msg00265.txt.bz2 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 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: ... 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 , dest=0x17f1fdc ) 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.