b5329c1d85
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. |
||
|---|---|---|
| bin | ||
| crypto | ||
| dist | ||
| distrib | ||
| doc | ||
| etc | ||
| games | ||
| gnu | ||
| include | ||
| lib | ||
| libexec | ||
| regress | ||
| rescue | ||
| sbin | ||
| share | ||
| sys | ||
| tools | ||
| usr.bin | ||
| usr.sbin | ||
| build.sh | ||
| BUILDING | ||
| Makefile | ||
| Makefile.inc | ||
| UPDATING | ||