Re: panic: in_pcblookup_local (?)

On Thursday, May 02, 2013 5:27:39 am Robert N. M. Watson wrote:
> 
> On 2 May 2013, at 01:57, Glen Barber wrote:
> 
> > So, I am admittedly not too familiar with DDB.  In fact, I just now
> > realize the kernel is built without DDB...
> 
> DDB is a very powerful tool in that it's been custom-developed to help debug common kernel panics. It lacks some of the flexibility, and especially the data-type awareness 
of GDB, but GDB is a less well-suited tool when investigating common crash patterns. I'll usually start out debugging in DDB, and find that 90% of my in-development panics 
can be debugged with it, resorting to GDB for post-mortem analyses in production or particularly hard debugging cases (usually where DDB's pretty printers for data types fall 
short). I've wanted, for a long time, to teach DDB how to pretty-print arbitrary types using DTrace's CTF meta-data, which would address the most significant major case where 
I turn to GDB. Mind you, the limitations I see in GDB are made up for in most part by John's GDB scripts :-).

Heh, I prefer DDB for active development as well, but after being forced to
work in an environment where I had to largely do post-mortem analysis, I had
to get a gdb environment that was close to as functional.  Also, using kgdb
on a live system to obtain info is less invasive than ddb (doesn't halt the
system), and you can easily add new scripts to generate useful reports without
having to recompile or reboot.

-- 
John Baldwin