From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Flush ^running
Date: Sat, 04 Oct 2008 18:16:00 -0000 [thread overview]
Message-ID: <20081004181529.GB27513@caradoc.them.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2008-10-04 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-04 15:02 Vladimir Prus
2008-10-04 18:16 ` Daniel Jacobowitz [this message]
2008-10-06 13:49 ` Marc Khouzam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081004181529.GB27513@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox