aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2011-12-14 14:46:24 +0000
committerPedro Alves <palves@redhat.com>2011-12-14 14:46:24 +0000
commit2fb860fcbc80b76dbd84958e547ddf1bdd1c4417 (patch)
tree02f4af0e43c6436a80e0282de46271744d9d6344 /gdb
parentad32032e2e1a386cbda9879e796125d2e0301dc9 (diff)
downloadgdb-2fb860fcbc80b76dbd84958e547ddf1bdd1c4417.zip
gdb-2fb860fcbc80b76dbd84958e547ddf1bdd1c4417.tar.gz
gdb-2fb860fcbc80b76dbd84958e547ddf1bdd1c4417.tar.bz2
2011-12-14 Pedro Alves <pedro@codesourcery.com>
* gdb.texinfo (Implementing a Remote Stub): Explain that you should transfer control to the stub in the startup code instead of in main. Mention the need to get past the initial breakpoint.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/doc/ChangeLog6
-rw-r--r--gdb/doc/gdb.texinfo15
2 files changed, 18 insertions, 3 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index b295a48..6cd0b9b 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,9 @@
+2011-12-14 Pedro Alves <pedro@codesourcery.com>
+
+ * gdb.texinfo (Implementing a Remote Stub): Explain that you
+ should transfer control to the stub in the startup code instead of
+ in main. Mention the need to get past the initial breakpoint.
+
2011-12-06 Tom Tromey <tromey@redhat.com>
* gdb.texinfo (Set Breaks): Update for new behavior.
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 50c299e..925e66a 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -17536,8 +17536,8 @@ subroutines:
@findex set_debug_traps
@cindex remote serial stub, initialization
This routine arranges for @code{handle_exception} to run when your
-program stops. You must call this subroutine explicitly near the
-beginning of your program.
+program stops. You must call this subroutine explicitly in your
+program's startup code.
@item handle_exception
@findex handle_exception
@@ -17683,13 +17683,22 @@ Make sure you have defined the supporting low-level routines
@end display
@item
-Insert these lines near the top of your program:
+Insert these lines in your program's startup code, before the main
+procedure is called:
@smallexample
set_debug_traps();
breakpoint();
@end smallexample
+On some machines, when a breakpoint trap is raised, the hardware
+automatically makes the PC point to the instruction after the
+breakpoint. If your machine doesn't do that, you may need to adjust
+@code{handle_exception} to arrange for it to return to the instruction
+after the breakpoint on this first invocation, so that your program
+doesn't keep hitting the initial breakpoint instead of making
+progress.
+
@item
For the 680x0 stub only, you need to provide a variable called
@code{exceptionHook}. Normally you just use: