[issue1672] panic (trap 12) around btree_search() in 2.4.1-RELEASE

["Joe \"Floid\" Kanowitz \(via DragonFly issue tracker\)" <sinknull@xxxxxxxxxxxxxxxxxxxxx>]

Joe "Floid" Kanowitz <jkanowitz@snet.net> added the comment:

>    Methinks the panic message must have scrolled off the screen
>    (it would have been above the backtrace).  The trap below the
>    trace was probably a double-fault in the debugger.

I'm still learning my way around the debugger - this is that 'production'
machine set up with a serial console and I only drape the cable across the room
when it acts up.  The 'trap below' was from an intentional show command, pardon
any ambiguity.

What's the right way to retrieve the actual panic string after you've entered
ddb?  Or is there none?  [The msgbuf didn't seem to have it.]

>    Definitely set up your dumpdev so we can get a dump if this 
>    occurs for you again.  There have been a couple of assertions
>    fixed in 2.5.x that have not been MFCd to 2.4.x due to the
>    HAMMER codebase diverging too much between 2.4.x and 2.5.x.

Yup, set up properly now.

_____________________________________________________
DragonFly issue tracker <bugs@lists.dragonflybsd.org>
<http://bugs.dragonflybsd.org/issue1672>
_____________________________________________________