public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jens.elmenthaler at advantest dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/18622] New: Erroneous "running" event while in suspended state messing up Eclipse DSF
Date: Fri, 03 Jul 2015 13:31:00 -0000 [thread overview]
Message-ID: <bug-18622-4717@http.sourceware.org/bugzilla/> (raw)
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.
next reply other threads:[~2015-07-03 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 13:31 jens.elmenthaler at advantest dot com [this message]
2022-05-25 17:49 ` [Bug mi/18622] " tromey at sourceware dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-18622-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).