This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Flush ^running


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]