This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/15434] New: Dprintf uses a synchronous 'continue' even in non-stop mode
- From: "marc.khouzam at ericsson dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 06 May 2013 02:25:50 +0000
- Subject: [Bug breakpoints/15434] New: Dprintf uses a synchronous 'continue' even in non-stop mode
- Auto-submitted: auto-generated
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.