From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-13600-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 28571 invoked by alias); 6 May 2013 02:25:51 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Received: (qmail 28516 invoked by uid 48); 6 May 2013 02:25:51 -0000
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: breakpoints
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marc.khouzam at ericsson dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-15434-4717@http.sourceware.org/bugzilla/>
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
X-SW-Source: 2013-q2/txt/msg00189.txt.bz2

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.