From: Andi Kleen <ak@suse.de>
To: Michael Sinz <msinz@wgate.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Core dump file control
Date: 14 Feb 2002 17:37:46 +0100 [thread overview]
Message-ID: <p73lmdw10kl.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <3C6BE18F.7B849129@wgate.com.suse.lists.linux.kernel>
In-Reply-To: Michael Sinz's message of "14 Feb 2002 17:15:32 +0100"
Michael Sinz <msinz@wgate.com> writes:
>
> This then causes core dumps to be of the format:
>
> /coredumps/whale.sinz.org-badprogram-13917.core
I had something like this for a long time on my todo list. The idea
was to set core_name_format to the name of a named pipe and have an
daemon on the other end that logs backtraces to syslogd (something a
bit like dr.watson)
Only problem is that it won't handle parallel coredumps very well
without some additional (deadlock prone) global locking or alternatively
support AF_UNIX stream sockets too that have the concept of multiple
streams over a single name.
-Andi
next parent reply other threads:[~2002-02-14 16:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C6BE18F.7B849129@wgate.com.suse.lists.linux.kernel>
2002-02-14 16:37 ` Andi Kleen [this message]
[not found] ` <363c044a047f1f07d2@[192.168.1.4]>
2002-02-14 17:09 ` [PATCH] Core dump file control Michael Sinz
2002-02-15 17:57 Michael Sinz
2002-02-15 19:07 ` Michael Sinz
2002-02-16 17:37 ` Horst von Brand
2002-02-17 14:36 ` Michael Sinz
[not found] <361c88b8047e6c07d2@[192.168.1.4]>
2002-02-14 17:53 ` Michael Sinz
-- strict thread matches above, loose matches on Subject: below --
2002-02-14 16:10 Michael Sinz
2002-02-15 11:40 ` Jakob Østergaard
2002-02-15 11:44 ` Martin Dalecki
2002-02-15 12:11 ` Michael Sinz
2002-02-15 12:13 ` Jakob Østergaard
2002-02-15 12:22 ` Martin Dalecki
2002-02-15 12:32 ` Jakob Østergaard
2002-02-15 12:55 ` Michael Sinz
2002-02-15 12:06 ` Michael Sinz
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=p73lmdw10kl.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=msinz@wgate.com \
/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