Date: Thu, 12 Mar 1998 11:18:58 +1030 From: Greg Lehey <grog@lemis.com> To: Alexander Litvin <archer@lucky.net>, current@FreeBSD.ORG Subject: Re: Softupdates code not Prime Time yet. Message-ID: <19980312111858.40450@freebie.lemis.com> In-Reply-To: <199803112332.BAA02402@grape.carrier.kiev.ua>; from Alexander Litvin on Thu, Mar 12, 1998 at 01:32:38AM %2B0200 References: <19980311195045.19668.qmail@iquest7.iquest.net> <199803112332.BAA02402@grape.carrier.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 12 March 1998 at 1:32:38 +0200, Alexander Litvin wrote:
> In article <19980311195045.19668.qmail@iquest7.iquest.net> you wrote:
>>>
>>> I have to echo what Julian is saying additionally if you are not prepared
>>> to give a kernel stack trace and possibly nice printfs of kernel data
>>> structures then don't try soft updates. I hate bug reports like
>>> "soft update crashed my system" 8)
>>>
>> Pretty much the same with the VM and NFS stuff that I have been
>> working on. Please, whenever you have problems with the kernel,
>> a traceback and other such information is very useful. Alot
>> of traffic for the VM and NFS stuff happens in the background,
>> where the groups don't see it... People who know the issues
>> about working on the kernel, also generally know that a statement
>> about a crash without any kind of information is useless, and
>> often just gets ignored.
>
>> IF one sends the output of a panic only, without the appropriate
>> portion of the namelist, the info is useless.
>
> Sorry, but it would be much easier if it were possible to
> boot stripped kernels.
I don't think there's any particular problem with booting stripped
kernels (modulo some problems reported with strip recently). But I
agree wholeheartedly that bug fixing is a pain without a minumum of
information. What do people say about making something like this a
policy?
1. Build a kernel with debugging avaialable.
2. Enable dumps.
3. If you wish, strip the kernel before booting, but keep the debug
version in /var/crash for later analysis.
Greg
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980312111858.40450>