public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/18360] New: Crash when using "interrupt -a"
@ 2015-04-30 15:13 simon.marchi at ericsson dot com
0 siblings, 0 replies; only message in thread
From: simon.marchi at ericsson dot com @ 2015-04-30 15:13 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=18360
Bug ID: 18360
Summary: Crash when using "interrupt -a"
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: simon.marchi at ericsson dot com
Target Milestone: ---
Created attachment 8292
--> https://sourceware.org/bugzilla/attachment.cgi?id=8292&action=edit
Test source file to reproduce.
When I have one thread stopped on a (conditional) breakpoint and the others
running, interrupt -a crashes gdb. I am using "GNU gdb (GDB)
7.9.50.20150428-cvs".
Here is the transcript, see attached file for source.
$ gcc -g3 -O0 test.c -o test -pthread
$ gdb -nx test
Reading symbols from test...done.
(gdb) set non-stop on
(gdb) b 15 if arg->num == 2
Breakpoint 1 at 0x40065d: file test.c, line 15.
(gdb) r
Starting program: /tmp/test
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff77f6700 (LWP 13451)]
[New Thread 0x7ffff6ff5700 (LWP 13452)]
[New Thread 0x7ffff67f4700 (LWP 13453)]
[New Thread 0x7ffff5ff3700 (LWP 13454)]
Breakpoint 1, thread_func (varg=0x7fffffffe058) at test.c:15
15 a++;
(gdb) [New Thread 0x7ffff57f2700 (LWP 13455)]
i th
Id Target Id Frame
6 Thread 0x7ffff57f2700 (LWP 13455) "test" (running)
5 Thread 0x7ffff5ff3700 (LWP 13454) "test" (running)
4 Thread 0x7ffff67f4700 (LWP 13453) "test" thread_func
(varg=0x7fffffffe058) at test.c:15
3 Thread 0x7ffff6ff5700 (LWP 13452) "test" (running)
2 Thread 0x7ffff77f6700 (LWP 13451) "test" (running)
* 1 Thread 0x7ffff7fca740 (LWP 13447) "test" (running)
(gdb) interrupt -a
../../../src/binutils-gdb/gdb/inline-frame.c:338: internal-error:
skip_inline_frames: Assertion `find_inline_frame_state (ptid) == NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-04-30 15:13 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-04-30 15:13 [Bug gdb/18360] New: Crash when using "interrupt -a" simon.marchi at ericsson dot com
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).