atatat b5329c1d85 (1) Don't print the message buffer (via ddb's dmesg command) if the ... message buffer has not yet been set up, mimicking code from the top of the sysctl routine for retrieving the message buffer. (2) Add a /l modifier to the trace command. This makes it print the backtrace using printf() instead of db_printf(), which has the nice side-effect of also putting it into the message buffer. A kernel with ddb in it but disabled (ie, ddb.onpanic set to zero) will print a backtrace (which ends up in the message buffer) before dumping (or not, depending on the value of kern.dump_on_panic) and rebooting, but if ddb is not disabled, the backtrace is not printed, and there's no way to get it to display a backtrace such that you can retrieve it after the dump. The backtrace printed by gdb is sometimes a little different. (3) Documentation for the above.		2003-05-15 13:18:18 +00:00
..
man0	Drop trailing whitespace. Reviewed by wiz.	2003-05-06 10:46:41 +00:00
man1
man3
man4	(1) Don't print the message buffer (via ddb's dmesg command) if the	2003-05-15 13:18:18 +00:00
man5	Add cross-references to w(1) and lastlogin(8).	2003-05-14 18:07:01 +00:00
man6
man7	New sentence, new line.	2003-05-08 04:48:27 +00:00
man8	setup -> set up.	2003-05-15 06:01:02 +00:00
man9	setup -> set up.	2003-05-14 12:00:33 +00:00
tools	Drop trailing whitespace. Reviewed by wiz.	2003-05-06 10:46:41 +00:00
Makefile