From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [MI, doc] flush output in -gdb-exit
Date: Thu, 17 Dec 2009 13:13:00 -0000 [thread overview]
Message-ID: <20091217131332.GA15129@caradoc.them.org> (raw)
In-Reply-To: <200912171046.03355.vladimir@codesourcery.com>
On Thu, Dec 17, 2009 at 10:46:03AM +0300, Vladimir Prus wrote:
>
> I've noticed that under frontend, -gdb-exit may "timeout", even though it sends "^exit"
> immediately. There was a flush missing. This patch adds it, and clarifies that frontend
> should wait for GDB to actually exit, not just acknoledge the request.
>
> OK?
This is OK (with changelog), although I don't see why it's necessary -
when we exit, shouldn't that flush stdout?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-12-17 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 7:46 Vladimir Prus
2009-12-17 13:13 ` Daniel Jacobowitz [this message]
2009-12-17 14:01 ` Vladimir Prus
2009-12-17 15:12 ` Daniel Jacobowitz
2009-12-17 19:54 ` Eli Zaretskii
2009-12-21 10:02 ` Vladimir Prus
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=20091217131332.GA15129@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--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