A few questions:
- How did the system crash? Does 'stat' show an exception, or a
panic case, or ... ?
- Based on that, can you 'deftask' to the failing process' address.
Let's say that the failing process ID is 1538. From there, you can
'task | grep 1538'. The first address given (0xdefdb000, for
example ... it will more than likely be different for your case)
can be used as the argument to deftask. Then 't' will report the
stack trace for the default task.
So, in short, 'stat' to find the failing process/process ID, 'task'
to show the current set of processes, using 'grep' to find the right
task based on the process ID, failing CPU, etc., and 'deftask' to
the base address of the task.
Thanks, Kim.
--Matt
On Tue, 16 Oct 2001, Kim Le wrote:
|>Hi All,
|>
|>I am new to lkcd and not sure how to use it. I hope anyone can help me to
|>get started.
|>
|>I installed lkcd and able to collect crash dump in to
|>/var/log/vmdump/vmdump.1. Along with that is analysis.1 crash.1.
|>
|>Now my question is how can I perform stack trace to know where my code is
|>crash. I tried to run crash.1 then trace command but it keep complaining
|>that no default task defined.
|>
|>Is there any quick usage guide for lkcd that I can look at ?
|>
|>Thanks in advance for any help.
|>
|>Kim
|>
|