how to get more info #2

[John-Mark Gurney]

John Baldwin wrote this message on Wed, Dec 21, 2005 at 11:16 -0500:
> On Wednesday 21 December 2005 03:53 am, David Reid wrote:
> > Following on from my last attempt to get more information on why my box
> > keeps rebooting, it was suggested that the lack of panics was a function
> > of running  under X. Off list it was suggested I try remote debugging
> > via firewire, something I have now done.
> >
> > The panic showed up in vm_map_entry_splay as a page fault. The function
> > was called following a trap 0xc.
> >
> > I tried to get into gdb to get more information but it complained about
> > a lack of remote debuggers.
> >
> > As I'm still new to the remote debugging thing does anyone have any
> > pointers/suggestions for how to extract more information next time it
> > crashes and what sort of information I should post?
> 
> Compile KDB and DDB into the kernel.  You can then use 'tr' in ddb to get a 
> stack trace.

add option GDB if you want to try to use gdb w/ it too.  Though ddb is
usually enough for basic stuff like getting a back trace like jhb said
above...

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."