Add comment that gdb and pintos have to run on the same machine.
authorBen Pfaff <blp@cs.stanford.edu>
Tue, 20 Dec 2005 07:33:37 +0000 (07:33 +0000)
committerBen Pfaff <blp@cs.stanford.edu>
Tue, 20 Dec 2005 07:33:37 +0000 (07:33 +0000)
doc/debug.texi

index 1c6d7a39e584aa4577b58bed2e80a4092e98b70f..6432ca3a1fa530a9a13af7710a4d4f8d3f535ef1 100644 (file)
@@ -250,6 +250,12 @@ gdb kernel.o
 target remote localhost:1234
 @end example
 
+(If the @command{target remote} command fails, then make sure that both
+@command{gdb} and @command{pintos} are running on the same machine by
+running @command{hostname} in each terminal.  If the names printed
+differ, then you need to open a new terminal for @command{gdb} on the
+machine running @command{pintos}.)
+
 Now @command{gdb} is connected to the simulator over a local
 network connection.  You can now issue any normal @command{gdb}
 commands.  If you issue the @samp{c} command, the simulated BIOS will take