public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "marc.khouzam at ericsson dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/15434] New: Dprintf uses a synchronous 'continue' even in non-stop mode
Date: Mon, 06 May 2013 02:25:00 -0000 [thread overview]
Message-ID: <bug-15434-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=15434
Bug #: 15434
Summary: Dprintf uses a synchronous 'continue' even in non-stop
mode
Product: gdb
Version: 7.5
Status: NEW
Severity: normal
Priority: P2
Component: breakpoints
AssignedTo: unassigned@sourceware.org
ReportedBy: marc.khouzam@ericsson.com
Classification: Unclassified
In non-stop mode, when hitting a dprintf, that dprintf resumes execution with a
'continue' command. This blocks the asynchronous I/O of GDB, which prevents a
frontend from interacting with it. In non-stop mode, MI mode always does an
asynchronous continue, but dprintf does not; therefore hitting a dprintf brings
GDB in a state that is not expected by the frontend.
I'm pretty sure this will be solved when fixing Bug 15075, but I was told it is
better to open all bugs to make sure every known problem is resolved.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2013-05-06 2:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 2:25 marc.khouzam at ericsson dot com [this message]
2013-05-13 6:53 ` [Bug breakpoints/15434] " teawater at gmail dot com
2013-05-13 6:55 ` teawater at gmail dot com
2013-05-13 6:59 ` teawater at gmail dot com
2013-05-13 7:00 ` teawater at gmail dot com
2013-05-13 17:07 ` marc.khouzam at ericsson dot com
2013-05-13 17:12 ` marc.khouzam at ericsson dot com
2013-05-14 12:14 ` teawater at gmail dot com
2013-05-16 7:30 ` teawater at gmail dot com
2013-06-25 11:37 ` cvs-commit at gcc dot gnu.org
2013-06-25 11:42 ` teawater at gmail dot com
2013-06-26 2:32 ` cvs-commit at gcc dot gnu.org
2013-06-26 2:32 ` cvs-commit at gcc dot gnu.org
2014-01-10 16:01 ` marc.khouzam at ericsson dot com
2021-09-22 16:58 ` mervegunesli at aol dot com
2021-09-22 17:01 ` mark at klomp 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-15434-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).