This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/18717] New: gdb misbehaves if non-leader thread exits process
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 24 Jul 2015 17:18:01 +0000
- Subject: [Bug gdb/18717] New: gdb misbehaves if non-leader thread exits process
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=18717
Bug ID: 18717
Summary: gdb misbehaves if non-leader thread exits process
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: palves at redhat dot com
Target Milestone: ---
This affects both the native backend and gdbserver.
If a non-leader thread exits the process while all other threads are
ptrace-stopped, native gdb internal-errors.
I'm adding a test to the testsuite that catches this:
/home/pedro/gdb/mygit/build/../src/gdb/linux-nat.c:3198: internal-error:
linux_nat_filter_event: Assertion `lp->resumed' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
FAIL: gdb.threads/non-leader-exit-process.exp: program exits normally (GDB
internal error)
--
You are receiving this mail because:
You are on the CC list for the bug.