Bug 14112
| Summary: | calls in ddb doc don't exist any longer | ||
|---|---|---|---|
| Product: | Documentation | Reporter: | Thierry.Besancon <Thierry.Besancon> |
| Component: | Books & Articles | Assignee: | freebsd-doc (Nobody) <doc> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | CC: | besancon |
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
State Changed From-To: open->closed Updated the section, thanks. |
Trying to debug a kernel, I started lynx and read in the section "On-line Kernel Debugging Using DDB" : ... Now you have now examined why your kernel failed, and you wish to reboot. Remember that, depending on the severity of previous malfunctioning, not all parts of the kernel might still be working as expected. Perform one of the following actions to shut down and reboot your system: call diediedie() This will cause your kernel to dump core and reboot, so you can later analyze the core on a higher level with kgdb. This command usually must be followed by another continue statement. There is now an alias for this: panic. call boot(0) Which might be a good way to cleanly shut down the running system, sync() all disks, and finally reboot. ... Well, diediedie() or boot() are undefined symbols in the FreeBSD 3.3 release. Fix: Find the correct symbols. How-To-Repeat: No need in repeating.