Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: eliz@gnu.org, gdb-patches@sources.redhat.com
Subject: [PATCH] BSD libkvm documentation
Date: Sat, 03 Jul 2004 13:32:00 -0000	[thread overview]
Message-ID: <200407031332.i63DWFeQ021626@elgar.kettenis.dyndns.org> (raw)

Eli, are these doc bits OK?

Mark


Index: doc/ChangeLog
from  Mark Kettenis  <kettenis@gnu.org>

	* gdb.texinfo (BSD libkvm Interface): New node (section)
	(Native): Add it to the menu.

Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.207
diff -u -p -r1.207 gdb.texinfo
--- doc/gdb.texinfo 19 Jun 2004 17:33:44 -0000 1.207
+++ doc/gdb.texinfo 3 Jul 2004 13:31:22 -0000
@@ -11412,6 +11412,7 @@ configurations.
 
 @menu
 * HP-UX::                       HP-UX
+* BSD libkvm Interface::	Debugging BSD kernel memory images
 * SVR4 Process Information::    SVR4 process information
 * DJGPP Native::                Features specific to the DJGPP port
 * Cygwin Native::		Features specific to the Cygwin port
@@ -11424,6 +11425,47 @@ On HP-UX systems, if you refer to a func
 begins with a dollar sign, @value{GDBN} searches for a user or system
 name first, before it searches for a convenience variable.
 
+@node BSD libkvm Interface
+@subsection BSD libkvm Interface
+
+@kindex libkvm
+@cindex kernel memory image
+@cindex kernel crash dump
+
+BSD-derived systems (FreeBSD/NetBSD/OpenBSD) have a kernel memory
+interface that provides a uniform interface for accessing kernel virtual
+memory images, including live systems and crash dumps.  @value{GDBN}
+uses this interface to allow you to debug live kernels and kernel crash
+dumps on many native BSD configurations.  This is implemented as a
+special @code{kvm} debugging target.  For debugging a live system, load
+the currently running kernel into @value{GDBN} and connect to the
+@code{kvm} target:
+
+@smallexample
+(@value{GDBP}) @b{target kvm}
+@end smallexample
+
+For debugging crash dumps, provide the file name of the crash dump as an
+argument:
+
+@smallexample
+(@value{GDBP}) @b{target kvm /var/crash/bsd.0}
+@end smallexample
+
+Once connected to the @code{kvm} target, the following commands are
+available:
+
+@table @code
+@kindex kvm pcb
+@item kvm pcb
+Set current context from pcb address.
+
+@kindex kvm proc
+@item kvm proc
+Set current context from proc address.  This command isn't available on
+modern FreeBSD systems.
+@end table
+
 @node SVR4 Process Information
 @subsection SVR4 process information
 


             reply	other threads:[~2004-07-03 13:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-03 13:32 Mark Kettenis [this message]
2004-07-03 21:09 ` Eli Zaretskii
2004-07-04  7:03   ` Mark Kettenis
2004-07-04 19:14     ` Eli Zaretskii
2004-07-05 16:04       ` Mark Kettenis
2004-07-09 18:52     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200407031332.i63DWFeQ021626@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox