From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: psmith@gnu.org
Cc: gdb@sourceware.org
Subject: Re: Partial cores using Linux "pipe" core_pattern
Date: Mon, 18 May 2009 06:05:00 -0000 [thread overview]
Message-ID: <8ac60eac0905172304t4deae98bxbd4f0b1d2186a8a0@mail.gmail.com> (raw)
In-Reply-To: <1242609756.2800.135.camel@homebase.localnet>
On Sun, May 17, 2009 at 6:22 PM, Paul Smith <psmith@gnu.org> wrote:
> I've instrumented every single function with checking for errors and
> writing issues to syslog (including informational messages so I know the
> logging works) and no errors are printed. The size of the core that I
> get from read(2)'ing stdin is just short, but read(2) never fails or
> shows any errors!
You can't be read(2)ing stdin, since read(2) doesn't take FILE*.
Are you doing read(0, ...) or are you doing fread(..., stdin) ?
If the latter, are you handling the feof() vs. ferror() difference
correctly? A small code sample might help.
Cheers,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2009-05-18 6:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 1:23 Paul Smith
2009-05-18 6:05 ` Paul Pluzhnikov [this message]
2009-05-18 13:22 ` Paul Smith
2009-05-18 7:25 ` Andi Kleen
2009-05-18 13:29 ` Paul Smith
2009-05-18 13:49 ` Andreas Schwab
2009-05-18 14:32 ` Paul Smith
2009-05-21 16:32 ` Paul Smith
2009-05-26 19:26 ` Paul Smith
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=8ac60eac0905172304t4deae98bxbd4f0b1d2186a8a0@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=gdb@sourceware.org \
--cc=psmith@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