Page MenuHomeFreeBSD

D56868.id177367.diff
No OneTemporary

D56868.id177367.diff

diff --git a/documentation/content/en/books/developers-handbook/kerneldebug/_index.adoc b/documentation/content/en/books/developers-handbook/kerneldebug/_index.adoc
--- a/documentation/content/en/books/developers-handbook/kerneldebug/_index.adoc
+++ b/documentation/content/en/books/developers-handbook/kerneldebug/_index.adoc
@@ -77,12 +77,12 @@
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 @@
====
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 @@
== 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.

File Metadata

Mime Type
text/plain
Expires
Thu, Jul 2, 7:36 PM (12 h, 23 m)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
32771636
Default Alt Text
D56868.id177367.diff (1 KB)

Event Timeline