mirrors/binutils-gdb
0
0
Fork 0
mirror of https://sourceware.org/git/binutils-gdb.git synced 2024-11-30 21:44:19 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

* gdbinv-s.texi (Debug Session): Document exceptionHook.

Browse Source
This commit is contained in:
Jim Kingdon 1993-06-09 18:12:35 +00:00
parent 4640902b79
commit 49f09e1865
2 changed files with 24 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/doc/ChangeLog
View File

@ -1,3 +1,7 @@
Wed Jun 9 10:58:16 1993 Jim Kingdon (kingdon@cygnus.com)
* gdbinv-s.texi (Debug Session): Document exceptionHook.
Tue Jun 8 13:42:04 1993 Jim Kingdon (kingdon@cygnus.com) Tue Jun 8 13:42:04 1993 Jim Kingdon (kingdon@cygnus.com)
* gdb.texinfo (Print Settings): Move all stuff relating to symbolic * gdb.texinfo (Print Settings): Move all stuff relating to symbolic

23
gdb/doc/gdbinv-s.texi
View File

@ -55,18 +55,21 @@ machine; for example, use @file{sparc-stub.c} to debug programs on
@cindex remote serial stub list @cindex remote serial stub list
These working remote stubs are distributed with @value{GDBN}: These working remote stubs are distributed with @value{GDBN}:
@c FIXME! verify these...
@table @code @table @code
@item sparc-stub.c @item sparc-stub.c
@kindex sparc-stub.c @kindex sparc-stub.c
For @sc{sparc} architectures. For @sc{sparc} architectures.
@item m68k-stub.c @item m68k-stub.c
@kindex m68-stub.c @kindex m68k-stub.c
@kindex Motorola 680x0
@kindex 680x0
For Motorola 680x0 architectures. For Motorola 680x0 architectures.
@item i386-stub.c @item i386-stub.c
@kindex i36-stub.c @kindex i386-stub.c
@kindex Intel
@kindex 386
For Intel 386 and compatible architectures. For Intel 386 and compatible architectures.
@end table @end table
@ -204,6 +207,20 @@ set_debug_traps();
breakpoint(); breakpoint();
@end example @end example
@item
For the 680x0 stub only, you need to provide a variable called
exceptionHook. Normally you just use
@example
void (*exceptionHook)() = 0;
@end example
but if you, before calling @code{set_debug_traps}, set it to point to
a function, that function will be called when the debugger continues
from a trap (for example, bus error) which causes the debugger to be
entered. It is passed one parameter---an @code{int} which is the
exception number.
@item @item
Compile and link together: your program, the @value{GDBN} debugging stub for Compile and link together: your program, the @value{GDBN} debugging stub for
your target architecture, and the supporting subroutines. your target architecture, and the supporting subroutines.