From: Owen Lucas <owen.lucas@student.adelaide.edu.au>
To: gcc-help@gcc.gnu.org
Subject: Re: problem piping stdout
Date: Mon, 02 Oct 2006 02:04:00 -0000 [thread overview]
Message-ID: <1159754662.452073a60479f@webmail.adelaide.edu.au> (raw)
In-Reply-To: <200610011628.31370.vda.linux@googlemail.com>
> Use strace to find out what is going on.
shows what I would expect
> Does it work if you do write(1, "foo bar\n", 8) instead of printf?
YES it does!
So why does that work and not printf?
owen
Quoting Denis Vlasenko <vda.linux@googlemail.com>:
>
> Use strace to find out what is going on.
>
> Does it work if you do write(1, "foo bar\n", 8) instead of printf?
> --
> vda
>
next prev parent reply other threads:[~2006-10-02 2:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1159709654.451fc3d67797a@webmail.adelaide.edu.au>
2006-10-01 13:55 ` Problem " Owen Lucas
2006-10-01 16:20 ` John (Eljay) Love-Jensen
[not found] ` <200610011628.31370.vda.linux@googlemail.com>
2006-10-02 2:04 ` Owen Lucas [this message]
[not found] <043c01c6e568$167abda0$a501a8c0@CAM.ARTIMI.COM>
2006-10-02 2:08 ` problem " Owen Lucas
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=1159754662.452073a60479f@webmail.adelaide.edu.au \
--to=owen.lucas@student.adelaide.edu.au \
--cc=gcc-help@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).