Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: psmith@gnu.org
Cc: Andi Kleen <andi@firstfloor.org>,  gdb@sourceware.org
Subject: Re: Partial cores using Linux "pipe" core_pattern
Date: Mon, 18 May 2009 13:49:00 -0000	[thread overview]
Message-ID: <m27i0ejzbi.fsf@igel.home> (raw)
In-Reply-To: <1242653371.2800.163.camel@homebase.localnet> (Paul Smith's 	message of "Mon, 18 May 2009 09:29:31 -0400")

Paul Smith <psmith@gnu.org> writes:

> On Mon, 2009-05-18 at 09:25 +0200, Andi Kleen wrote:
>> Paul Smith <psmith@gnu.org> writes:
>> >
>> > Does anyone have any thoughts about where I can look next to try to
>> > figure out what's going on?  Ideas or knowledge about limitations of the
>> > kernel's core_pattern pipe capability, such as timing issues etc., that
>> > might be leaving me with short cores?
>> 
>> Sounds more like a kernel problem to me. It would be good if you
>> could find out in what way the cores are truncated, then do a proper
>> kernel bug report.
>> 
>> Or add printks to the kernel coredumper and try to figure out this
>> way where/why it stops.
>
> Heh, I was afraid you'd say that :-).  OK, I'll dig into the kernel
> coredumper and add some printks etc.

Apparently the ELF core dumper cannot handle short writes (see
dump_write in fs/binfmt_elf.c).  You should probably use a read buffer
of at least a page, which is the most the kernel tries to write at once.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2009-05-18 13:49 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
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 [this message]
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=m27i0ejzbi.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=andi@firstfloor.org \
    --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