From eb7c0dcb6d4364f6079c066c73f836d7d37ff10b Mon Sep 17 00:00:00 2001 From: Joachim Nilsson Date: Sun, 25 Aug 2002 00:06:18 +0000 Subject: none --- Mach/RemoteDebugOskitMach.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Mach/RemoteDebugOskitMach.mdwn') 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 -- cgit v1.2.3