On Mon, Nov 22, 1999 at 10:49:47AM +0530, [EMAIL PROTECTED] wrote:
> Hello there,
> Well, i assume that when a panic occurs the stack is dumped with an
> Ooops Message. You should be able to copy that, only then can you
> know why and what and where all happened? You can use ksymoops
> to analyze that and maybe the 'guru's can point you towards something
> much better or you could try out remote debugging.
Remote debugging doesn't always work for unpredicatable bugs. Not
everybody has a spare machine to do the debugging. The best approach
is the in-kernel debugger - something Linus has irrationally resisted
for a long time.
SGI's kdb looks pretty good - I haven't used it myself though. I like
FreeBSD's Mach derived debugger too. When the panic happens, it drops
into the debugger for you to examine the state of the system. With
ksymoops, you're limited to what is dumped on the screen - which is
often insufficient information. SCO UnixWare ("The UNIX"), the other
OS I've worked on also has a solid kernel debugger (kdb).
-Arun
--------------------------------------------------------------------
The Linux India Mailing List Archives are now available. Please search
the archive at http://lists.linux-india.org/ before posting your question
to avoid repetition and save bandwidth.
