From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27136 invoked by alias); 4 Oct 2008 18:16:11 -0000 Received: (qmail 27127 invoked by uid 22791); 4 Oct 2008 18:16:11 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 04 Oct 2008 18:15:31 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id BA85310D22; Sat, 4 Oct 2008 18:15:29 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 9747310CF4; Sat, 4 Oct 2008 18:15:29 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KmBf7-0007En-1R; Sat, 04 Oct 2008 14:15:29 -0400 Date: Sat, 04 Oct 2008 18:16:00 -0000 From: Daniel Jacobowitz To: Vladimir Prus Cc: gdb-patches@sources.redhat.com Subject: Re: Flush ^running Message-ID: <20081004181529.GB27513@caradoc.them.org> Mail-Followup-To: Vladimir Prus , gdb-patches@sources.redhat.com References: <200810041901.40210.vladimir@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200810041901.40210.vladimir@codesourcery.com> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-10/txt/msg00108.txt.bz2 On Sat, Oct 04, 2008 at 07:01:40PM +0400, Vladimir Prus wrote: > > I've run into a case where gdb would not print ^running in response > to -exec-continue -- at least not during the time frontend is willing > to wait for the response. The problem only happened for my when gdb > is driven by a frontend, not on command line; I don't know what frontend > does differently. I've checked in the below patch to fix this. Try "cat | gdb -i=mi 2>&1 | cat" to reproduce this sort of thing. If isatty() returns true, most C runtime libraries will put stdout in unbuffered mode. -- Daniel Jacobowitz CodeSourcery