1
0
mirror of https://git.FreeBSD.org/doc.git synced 2026-06-02 19:35:07 +00:00

developers-handbook: Remove some refs to long-past-EOL versions

Reviewed by:	markj
Sponsored by:	The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D56868
This commit is contained in:
Ed Maste
2024-12-09 08:26:52 -05:00
parent 18cf6c7c4c
commit 6183910d61
@@ -77,12 +77,12 @@ Full memory dumps::
Hold the complete contents of physical memory.
Minidumps::
Hold only memory pages in use by the kernel (FreeBSD 6.2 and higher).
Hold only memory pages in use by the kernel.
Textdumps::
Hold captured, scripted, or interactive debugger output (FreeBSD 7.1 and higher).
Hold captured, scripted, or interactive debugger output.
Minidumps are the default dump type as of FreeBSD 7.0, and in most cases will capture all necessary information present in a full memory dump, as most problems can be isolated only using kernel state.
Minidumps are the default dump type, and in most cases will capture all necessary information present in a full memory dump, as most problems can be isolated only using kernel state.
[[config-dumpdev]]
=== Configuring the Dump Device
@@ -172,7 +172,6 @@ After rebooting, your system should save a dump in [.filename]#/var/crash# along
====
This section covers man:kgdb[1].
The latest version is included in the package:devel/gdb[].
An older version is also present in FreeBSD 11 and earlier.
====
To enter into the debugger and begin getting information from the dump, start kgdb:
@@ -551,7 +550,6 @@ Remember that it is hard to read the on-line manual while single-stepping the ke
== On-Line Kernel Debugging Using Remote GDB
The FreeBSD kernel provides a second KDB backend for on-line debugging: man:gdb[4].
This feature has been supported since FreeBSD 2.2, and it is actually a very neat one.
GDB has supported _remote debugging_ for a long time.
This is done using a very simple protocol along a serial line.