Sean McBride writes: <..>

This was on Darwin Dev on tuesday:

Thanks again (in public this time). Now that I can see the value, I've fixed my panic and everything seems to work just fine.

...

...

DB_KDB 0x10 This enables the kdb (serial) debugger instead of

...

...

gdb (not really new)

Cool!!! I'd like to try kdb, but I can't seem to make it work. If its as good as the FreeBSD/NetBSD ddb, I'd rather just use it than gdb. However, I can't seem to make it work. % nvram boot-args boot-args -v debug=0x11e However, when I send a break, it still ends up waiting for kdp. I've gone so far as to attempt to switch manually: (gdb) p *( int *)¤t_debugger $1 = 1 (gdb) p *( int *)&switch_debugger $2 = 0 (gdb) set *( int *)&switch_debugger=1 (gdb) set *( int *)¤t_debugger=2 (gdb) c Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. 0x00085ed4 in Debugger () <back in kdp, not kdb> Kdb seems to be present in the kernel: % nm /mach_kernel | grep kdb_trap 00085638 T _kdb_trap And I do have a serial console working. Any ideas? I suppose cross-building Apple's gdb on FreeBSD was worth it after all ;)

...

0x100 turns off the graphical, multilingual panic screen, and reverts to

...

the old text stack crawl.

The magic bullet for getting rid of the nice window. ;) Cheers, Drew _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.