This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Flush ^running
- From: Daniel Jacobowitz <drow at false dot org>
- To: Vladimir Prus <vladimir at codesourcery dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Sat, 4 Oct 2008 14:15:29 -0400
- Subject: Re: Flush ^running
- References: <200810041901.40210.vladimir@codesourcery.com>
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