From 974b26bf7771abf4341767834209adebae79fbb9 Mon Sep 17 00:00:00 2001 From: Sascha Wildner Date: Fri, 30 Mar 2007 09:08:57 +0000 Subject: [PATCH] Put debugging information into a section of its own. --- share/man/man7/vkernel.7 | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/share/man/man7/vkernel.7 b/share/man/man7/vkernel.7 index 7f569dd517..81e8ebb78e 100644 --- a/share/man/man7/vkernel.7 +++ b/share/man/man7/vkernel.7 @@ -29,7 +29,7 @@ .\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" -.\" $DragonFly: src/share/man/man7/vkernel.7,v 1.13 2007/03/16 13:42:11 swildner Exp $ +.\" $DragonFly: src/share/man/man7/vkernel.7,v 1.14 2007/03/30 09:08:57 swildner Exp $ .\" .Dd March 16, 2007 .Dt VKERNEL 7 @@ -175,6 +175,11 @@ while operating as a console which causes the virtual kernel to enter its internal .Xr ddb 4 debugger. +.Sh DEBUGGING +It is possible to directly gdb the virtual kernel's process. +It is recommended that you do a +.Ql handle SIGSEGV noprint +to ignore page faults processed by the virtual kernel itself. .Sh EXAMPLES A couple of steps are necessary in order to prepare the system to build and run a virtual kernel. @@ -258,10 +263,6 @@ cd /usr/obj/usr/src/sys/VKERNEL The .Xr reboot 8 command can be used to stop a virtual kernel. -.Ss Debugging the kernel -It is possible to directly gdb the virtual kernel's process. It is -recommended that you do a 'handle SIGSEGV noprint' to ignore page faults -taken by the virtual kernel itself (which it processes itself). .Sh SEE ALSO .Xr bridge 4 , .Xr tap 4 , -- 2.41.0