From: Matthew Wilcox <willy@debian.org>
To: Grant Grundler <grundler@puffin.external.hp.com>
Cc: Matthew Wilcox <willy@debian.org>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 2.4.6-pa5 crashes on B160L
Date: Mon, 9 Jul 2001 00:48:38 +0100 [thread overview]
Message-ID: <20010709004838.R6103@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200107082331.RAA09058@puffin.external.hp.com>; from grundler@puffin.external.hp.com on Sun, Jul 08, 2001 at 05:31:25PM -0600
On Sun, Jul 08, 2001 at 05:31:25PM -0600, Grant Grundler wrote:
> No. I don't think we should turn it off.
> Not until we can get memory core dumps on crashes like HPUX does.
So far, I've seen _one_ useful stack dump posted to this list. The others
have just caused extra hassle & confusion for our users. And that
one stack dump was from Ryan , after repeated to-ing-and-froing with a
repeatable problem -- so he could have turned on an option very easily.
> Isn't that what the stack dump is for?
It's only useful if you've also got the System.map. If we didn't do
the stack dump, the users would probably send more information which
came before the stack dump.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2001-07-08 23:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-08 15:21 [parisc-linux] 2.4.6-pa5 crashes on B160L Scott Ashcroft
2001-07-08 21:10 ` Matthew Wilcox
2001-07-08 23:31 ` Grant Grundler
2001-07-08 23:48 ` Matthew Wilcox [this message]
2001-07-09 1:20 ` Grant Grundler
2001-07-09 15:34 ` B132 dies too (was Re: [parisc-linux] 2.4.6-pa5 crashes on B160L) LaMont Jones
2001-07-09 1:41 ` [parisc-linux] 2.4.6-pa5 crashes on B160L Scott Ashcroft
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=20010709004838.R6103@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=grundler@puffin.external.hp.com \
--cc=parisc-linux@lists.parisc-linux.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