This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug mi/18622] New: Erroneous "running" event while in suspended state messing up Eclipse DSF
- From: "jens.elmenthaler at advantest dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 03 Jul 2015 13:31:33 +0000
- Subject: [Bug mi/18622] New: Erroneous "running" event while in suspended state messing up Eclipse DSF
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=18622
Bug ID: 18622
Summary: Erroneous "running" event while in suspended state
messing up Eclipse DSF
Product: gdb
Version: 7.6
Status: NEW
Severity: normal
Priority: P2
Component: mi
Assignee: unassigned at sourceware dot org
Reporter: jens.elmenthaler at advantest dot com
Target Milestone: ---
Created attachment 8409
--> https://sourceware.org/bugzilla/attachment.cgi?id=8409&action=edit
Patch to suppress event for all-stop mode
I'm debugging a multi-threaded software written in C++ using Eclipse DSF in
all-stop mode. The gdb version is "GNU gdb (GDB) Red Hat Enterprise Linux
7.6.1-51.1.el7".
>From time to time threads are spawned or exited and if gdb detects this while
being suspended, an event "*running,thread-id=all" is received. This makes
Eclipse DSF assume the inferior resumed, although the inferior is still
suspended.
I tracked it down to the function mi_on_resume() in mi-interp.c and developed a
simple patch, that seems to work fine for me at least.
--
You are receiving this mail because:
You are on the CC list for the bug.