This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug corefiles/19180] New: Quiting, after debugging a SIGKILLed process, crashes GDB
- From: "dilyan.palauzov at aegee dot org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 28 Oct 2015 18:32:34 +0000
- Subject: [Bug corefiles/19180] New: Quiting, after debugging a SIGKILLed process, crashes GDB
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=19180
Bug ID: 19180
Summary: Quiting, after debugging a SIGKILLed process, crashes
GDB
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: corefiles
Assignee: unassigned at sourceware dot org
Reporter: dilyan.palauzov at aegee dot org
Target Milestone: ---
I use GDB 7.10.50.20151028-cvs .
I start a process, attach to it with GDB, send SIGKILL to the process, then
enter in GDB:
(gdb) detach
Detaching from program: /usr/local/bin/gdb, process 388
ptrace: No such process.
(gdb) quit
A debugging session is active.
Inferior 1 [process 388] will be detached.
Quit anyway? (y or n) y
/git/binutils-gdb/gdb/linux-nat.c:1530: internal-error: linux_nat_detach:
Assertion `num_lwps (ptid_get_pid (inferior_ptid)) == 1' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
And at this moment I cannot press "y" or anything else.
--
You are receiving this mail because:
You are on the CC list for the bug.