summaryrefslogtreecommitdiff
path: root/Mach
diff options
context:
space:
mode:
authorJoachim Nilsson <joachim@gnufans.org>2002-08-25 00:06:18 +0000
committerJoachim Nilsson <joachim@gnufans.org>2002-08-25 00:06:18 +0000
commiteb7c0dcb6d4364f6079c066c73f836d7d37ff10b (patch)
tree88f443947d97317b15bbb066bea013aba5651a3e /Mach
parentde5275318a154efc5ba1aa0678885b631789db25 (diff)
none
Diffstat (limited to 'Mach')
-rw-r--r--Mach/RemoteDebugOskitMach.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/Mach/RemoteDebugOskitMach.mdwn b/Mach/RemoteDebugOskitMach.mdwn
index b661e7b8..0e922acd 100644
--- a/Mach/RemoteDebugOskitMach.mdwn
+++ b/Mach/RemoteDebugOskitMach.mdwn
@@ -53,7 +53,7 @@ Last you need to follow the instructions given below.
-d (enable serial port debugging, optional) GDB\_COM=2 (use a different port other then CONS\_COM, default is to use the same as CONS\_COM) BAUD=9600 (use this baud rate, optional, default is 9600)
-- (delimits the arguments passed to the oskit from those to the kernel)
root=hd0s2 (tell gnumach which is your root partition, in this case it's hd0s2)
-5. Now I suggest that you familiarize yourself with [the GDB documentation on remote debugging](http://vmlinux.org/doc/gdb/html/gdb_15.html#SEC129). If you pass the -d boot flag to oskit-mach, then it will automatically insert a breakpoint at main() and wait for further instructions from GDB over the serial line. Here's a simple example of how to attach GDB to a remote target over a serial line:
+5. Now I suggest that you familiarize yourself with [the GDB documentation](http://vmlinux.org/doc/gdb/), especially on remote debugging. If you pass the -d boot flag to oskit-mach, then it will automatically insert a breakpoint at main() and wait for further instructions from GDB over the serial line. Here's a simple example of how to attach GDB to a remote target over a serial line:
$ script # record the debugging session
$ gdb # assume you're in the oskit-mach build dir.
(gdb) file kernel