From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andi Kleen <andi@firstfloor.org>
Cc: paul@mad-scientist.net, Oleg Nesterov <oleg@redhat.com>,
linux-kernel@vger.kernel.org, stable@kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>,
Roland McGrath <roland@redhat.com>
Subject: Re: [PATCH] coredump: Retry writes where appropriate
Date: Mon, 1 Jun 2009 20:06:30 +0100 [thread overview]
Message-ID: <20090601200630.6b18bcc1@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20090601190914.GV1065@one.firstfloor.org>
On Mon, 1 Jun 2009 21:09:14 +0200
Andi Kleen <andi@firstfloor.org> wrote:
> On Mon, Jun 01, 2009 at 08:02:32PM +0100, Alan Cox wrote:
> > > If a program seems to be unresponsive the user could ^C, without
> > > realizing that it was really dumping core. Now when they are asked to
> > > produce the core so the problem can be debugged, they can't do it. Or,
> >
> > and get their prompt back, which is probably why they are banging ^C. If
> > they didn't want their prompt back at that point they'd still be
> > wondering why nothing was occuring at the point it said (core dumped)
>
> Maybe we need a background core dump?
You can pretty much implement that via the pipe handler if you care. Just
buffer aggressively.
For the general case however programs assume that when wait() returns
indicating the core dump occurred that they can immediately access the
dump (eg bug-buddy in Gnome)
Alan
next prev parent reply other threads:[~2009-06-01 19:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-31 5:33 Paul Smith
2009-05-31 10:18 ` Alan Cox
2009-05-31 14:03 ` Olivier Galibert
2009-05-31 16:31 ` Alan Cox
2009-05-31 16:49 ` Olivier Galibert
2009-05-31 17:46 ` Paul Smith
2009-05-31 16:56 ` Paul Smith
2009-06-01 16:12 ` Oleg Nesterov
2009-06-01 16:41 ` Alan Cox
2009-06-01 17:11 ` Oleg Nesterov
2009-06-01 17:46 ` Alan Cox
2009-06-01 18:23 ` Oleg Nesterov
2009-06-01 20:38 ` Roland McGrath
2009-06-01 22:32 ` Oleg Nesterov
2009-06-01 23:02 ` Roland McGrath
2009-06-02 0:08 ` Oleg Nesterov
2009-06-03 7:09 ` Roland McGrath
2009-06-04 3:15 ` Oleg Nesterov
2009-06-04 17:14 ` Roland McGrath
2009-06-23 17:31 ` Paul Smith
2009-06-23 19:37 ` Oleg Nesterov
2009-07-07 19:37 ` Oleg Nesterov
2009-06-02 8:21 ` Alan Cox
2009-06-02 15:29 ` Oleg Nesterov
2009-06-03 7:15 ` Roland McGrath
2009-06-03 14:05 ` Paul Smith
2009-06-01 17:36 ` Paul Smith
2009-06-01 17:49 ` Alan Cox
2009-06-01 18:39 ` Paul Smith
2009-06-01 19:02 ` Alan Cox
2009-06-01 19:09 ` Andi Kleen
2009-06-01 19:06 ` Alan Cox [this message]
2009-06-01 19:14 ` Andi Kleen
2009-06-01 19:51 ` Paul Smith
2009-06-01 20:20 ` Oleg Nesterov
2009-06-01 21:34 ` Alan Cox
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=20090601200630.6b18bcc1@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=paul@mad-scientist.net \
--cc=roland@redhat.com \
--cc=stable@kernel.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
all inboxes | Powered by JetHome®