On 11/15/14, 5:43 PM, John-Mark Gurney wrote:
John-Mark Gurney wrote this message on Sat, Nov 15, 2014 at 01:37 -0800:
So, I got remote kgdb working w/ bhyve, but kernel modules aren't

I'm getting:
(kgdb) bt
#0  kdb_enter (why=0xffffffff8102ee88 "panic", msg=<value optimized out>)
     at ../../../kern/subr_kdb.c:444
#1  0xffffffff8094aa79 in vpanic (fmt=<value optimized out>,
     ap=<value optimized out>) at ../../../kern/kern_shutdown.c:739
#2  0xffffffff8094a8c9 in kassert_panic (fmt=<value optimized out>)
     at ../../../kern/kern_shutdown.c:634
#3  0xffffffff8093583c in __mtx_lock_flags (c=0xfffff80002919720, opts=0,
 line=442) at ../../../kern/kern_mutex.c:217
#4  0xffffffff81c3e3a7 in ?? ()
#5  0xfffff80002a474a0 in ?? ()
#6  0xfffff80002919720 in ?? ()

Where those should be in the aesni.ko module...  If I run kgdb on a
local machine, it properly finds the kernel modules... Any hits on
how to fix this?

works for me..
the modules I'm debugging are not compiled in.
you have to have the modules in the standard place ONE THE GDB HOST.
I make a chroot with an image of the machine being debugged, PLUS the sources.
and then run kgdb from inside that chroot.

Also, any plans to support the Z2 write-watchpoint packet?

(kgdb) watch *(char *)0xfffff80002919708
Hardware watchpoint 1: *(char *) 18446735277659625224
(kgdb) c
Can't clear hardware watchpoints without the 'Z2' (write-watchpoint) packet

freebsd-virtualization@freebsd.org mailing list
To unsubscribe, send any mail to 

Reply via email to