From: Riku Voipio <riku.voipio@iki.fi>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] flush stdout after printing usage()
Date: Fri, 6 Feb 2009 16:33:39 +0200 [thread overview]
Message-ID: <20090206143339.GA10366@kos.to> (raw)
In-Reply-To: <4980D569.9060408@codemonkey.ws>
On Wed, Jan 28, 2009 at 04:00:09PM -0600, Anthony Liguori wrote:
> Lionel Landwerlin wrote:
>>> On Wed, Jan 28, 2009 at 02:10:42PM -0600, Anthony Liguori wrote:
>>>> Riku Voipio wrote:
>>>>> Without fflush() getting output from piped qemu is a bit random.
>>>>>
>>>> It should get flushed upon exit(). Perhaps the problem is that
>>>> we're using _exit() instead of exit()?
>>>>
>> _exit does not trigger callbacks registred with at_exit.
> Yes. The question is why is it being used? What at_exit handler are we
> trying to avoid.
Historic reasons? Just to "be safe" since system qemu uses atexit handlers?
I don't see any atexit handlers registered for linux-user (or bsd-user)
targets for current svn qemu. Definetly none registered at command line parsing
stage.
prev parent reply other threads:[~2009-02-06 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 18:47 [Qemu-devel] [PATCH] flush stdout after printing usage() Riku Voipio
2009-01-28 20:10 ` Anthony Liguori
2009-01-28 21:06 ` Riku Voipio
2009-01-28 21:51 ` Lionel Landwerlin
2009-01-28 22:00 ` Anthony Liguori
2009-02-06 14:33 ` Riku Voipio [this message]
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=20090206143339.GA10366@kos.to \
--to=riku.voipio@iki.fi \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).