From: Paul Smith <psmith@gnu.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: gdb@sourceware.org
Subject: Re: Partial cores using Linux "pipe" core_pattern
Date: Mon, 18 May 2009 13:29:00 -0000 [thread overview]
Message-ID: <1242653371.2800.163.camel@homebase.localnet> (raw)
In-Reply-To: <87ab5aq3dq.fsf@basil.nowhere.org>
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.
I do have problems getting a readily reproducible test case. It seems
timing related; I tried replacing my gzopen()/etc. calls with
uncompressed open()/etc. and that seemed to help; no more short cores.
And yet at other times I can dump the core through gzopen() no problem.
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith@gnu.org> Find some GNU make tips at:
http://www.gnu.org http://make.mad-scientist.us
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
next prev parent reply other threads:[~2009-05-18 13:29 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 [this message]
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=1242653371.2800.163.camel@homebase.localnet \
--to=psmith@gnu.org \
--cc=andi@firstfloor.org \
--cc=gdb@sourceware.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