Re: no kld in minidumps

From: Dmitry Pryanishnikov <dmitry_at_atlantis.dp.ua>
Date: Sun, 5 Nov 2006 03:43:25 +0200 (EET)
Hello!

   Well, maybe it's a little late to reply now, but anyway...

On Fri, 18 Aug 2006, Andriy Gapon wrote:
> on 18/08/2006 20:50 Dmitry Pryanishnikov said the following:
>>> BTW, has anyone contemplated or even done this - some sort of a script
>>> to automatically add all modules that were loaded at a time of crash ?
>>
>>   Hmm, isn't this the task for asf(8). If not, what is asf(8) for?
>
> This is a very nice command, thank you!
> But it does not seem to be directly applicable to postmortem situation
> i.e. crash dump debugging.

   Actually asf(8) _can_ be useful during crash dump analysis in the limited
yet quite common case when currently loaded kernel and modules are the same 
as they were during the crash. E.g. I've booted to singleuser mode with
fdc.ko loaded as a module, established crash dump device and then crashed the 
system with 'kldunload fdc.ko' (see kern/104079). After reboot I've got
a core dump which can't be analyzed corectly w/o symbols from fdc.ko:

root_at_homelynx# asf -kf /boot/kernel my.asf
root_at_homelynx# kgdb /boot/kernel/kernel.debug vmcore.7
...
(here 'bt' doesn't show frames which belong to fdc.ko and above)
...
(kgdb) source my.asf

Now 'bt' correctly shows all frames.


Sincerely, Dmitry
-- 
Atlantis ISP, System Administrator
e-mail:  dmitry_at_atlantis.dp.ua
nic-hdl: LYNX-RIPE
Received on Sun Nov 05 2006 - 00:43:38 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:02 UTC