From: Juho Hiltunen <1771570@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1771570] Re: qemu-aarch64 $program > $file doesn't pipe output to file in 2.12.0
Date: Fri, 18 May 2018 17:47:36 -0000 [thread overview]
Message-ID: <152666565666.2744.2828126064980578338.malone@gac.canonical.com> (raw)
In-Reply-To: 152647807950.16381.7444115224433592455.malonedeb@soybean.canonical.com
Running "unbuffer qemu-aarch64 $program > $file" allows to pipe the
output.
Is it intentional that I need to disable buffering to allow piping to
other processes? If yes, this issue can be closed.
further reading about unbuffer:
https://unix.stackexchange.com/questions/25372/turn-off-buffering-in-
pipe#25378
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1771570
Title:
qemu-aarch64 $program > $file doesn't pipe output to file in 2.12.0
Status in QEMU:
New
Bug description:
Running qemu-aarch64 $program > $file doesn't pipe anything to $file.
The file is created but empty.
qemu-aarch64 --help > $file works, so piping output in my system seems to work.
qemu-x86_64 $program > $file works, too.
I'm running version 2.12.0 build from source with ./configure && make
Output of uname -a:
Linux zhostname> 4.4.0-101-generic #124-Ubuntu SMP Fri Nov 10 18:29:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1771570/+subscriptions
next prev parent reply other threads:[~2018-05-18 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 13:41 [Qemu-devel] [Bug 1771570] [NEW] qemu-aarch64 $program > $file doesn't pipe output to file in 2.12.0 Juho Hiltunen
2018-05-18 17:47 ` Juho Hiltunen [this message]
2018-05-18 18:09 ` [Qemu-devel] [Bug 1771570] " Peter Maydell
2018-05-19 6:46 ` Juho Hiltunen
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=152666565666.2744.2828126064980578338.malone@gac.canonical.com \
--to=1771570@bugs.launchpad.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.