I have an amd64 domU on amd64 domO, all current. The domU may be a bit behind. I have not tried this on amd64 non-xen. On the domU, I run gdb on a program (that I can't share). This program isn't really 64-bit clean - that's why I want to run the debugger. It has its own malloc version, and I did the equivalent of "break Our_Free" and then ran it. On my ssh connection where I was doing this I got: Program received signal SIGTRAP, Trace/breakpoint trap. 0x00007f7ffd93375a in _lwp_unpark () from /usr/lib/libc.so.12 (gdb) i thr (gdb) threa [Current thread is 0 (process 34)] (gdb) i threads (gdb) next Single stepping until exit from function _lwp_unpark, which has no line number information. [and then nothing] On the console: NetBSD/amd64 (domU-in-question.ir.bbn.com) (console) login: panic: kernel diagnostic assertion "sigismember(&sp->sp_set, signo)" failed: file "/n0/netbsd-current/src/sys/kern/kern_sig.c", line 510 Begin traceback... copyright() at netbsd:__kernassert+0x2ab72 fatal protection fault in supervisor mode trap type 4 code 0 rip ffffffff803714e4 cs e030 rflags 10246 cr2 ffffa0000f39cd60 cpl 0 rsp ffffa0000f398810 panic: trap Faulted in mid-traceback; aborting... dump to dev 142,1 not possible rebooting... I will see about updating the domU and trying again and looking a bit further, but wanted to see if this seemed familiar.
Attachment:
pgpXrFTV6zVWg.pgp
Description: PGP signature