aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEd Maste <emaste@FreeBSD.org>2024-12-09 13:26:52 +0000
committerEd Maste <emaste@FreeBSD.org>2026-05-07 14:19:51 +0000
commit6183910d617e179c8e39d82125e3f63fab2b99a8 (patch)
tree619ce913ad8564781a4c5eba13282092fdb44d53
parent18cf6c7c4c7ceb182ccaa066e200371a7370657d (diff)
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
-rw-r--r--documentation/content/en/books/developers-handbook/kerneldebug/_index.adoc8
1 files changed, 3 insertions, 5 deletions
diff --git a/documentation/content/en/books/developers-handbook/kerneldebug/_index.adoc b/documentation/content/en/books/developers-handbook/kerneldebug/_index.adoc
index 006ae4178a..407042d805 100644
--- a/documentation/content/en/books/developers-handbook/kerneldebug/_index.adoc
+++ b/documentation/content/en/books/developers-handbook/kerneldebug/_index.adoc
@@ -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.