diff options
| author | Jim Kingdon <jkingdon@engr.sgi.com> | 1993-10-31 19:36:41 +0000 |
|---|---|---|
| committer | Jim Kingdon <jkingdon@engr.sgi.com> | 1993-10-31 19:36:41 +0000 |
| commit | ffbfe2502630d70738bb7a4b37ffa38554e6b24e (patch) | |
| tree | ed2380f34595e435e4b94fdbafcfecce0e370b93 | |
| parent | 30fb2a64952ef7425575259265b696151f0347eb (diff) | |
| download | gdb-ffbfe2502630d70738bb7a4b37ffa38554e6b24e.zip gdb-ffbfe2502630d70738bb7a4b37ffa38554e6b24e.tar.gz gdb-ffbfe2502630d70738bb7a4b37ffa38554e6b24e.tar.bz2 | |
* remote.texi (VxWorks Remote): Clarify that rebuilding VxWorks kernel
is a mandatory step. Make the stuff about that more concise.
| -rw-r--r-- | gdb/doc/ChangeLog | 5 | ||||
| -rw-r--r-- | gdb/doc/remote.texi | 26 |
2 files changed, 17 insertions, 14 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index ba1d56d..a3bd273 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,8 @@ +Sun Oct 31 13:31:10 1993 Jim Kingdon (kingdon@lioth.cygnus.com) + + * remote.texi (VxWorks Remote): Clarify that rebuilding VxWorks kernel + is a mandatory step. Make the stuff about that more concise. + Wed Oct 27 00:25:46 1993 Jim Kingdon (kingdon@lioth.cygnus.com) * stabs.texinfo (Class Names): New node. diff --git a/gdb/doc/remote.texi b/gdb/doc/remote.texi index 9073523..b580f0b 100644 --- a/gdb/doc/remote.texi +++ b/gdb/doc/remote.texi @@ -909,23 +909,21 @@ The following information on connecting to VxWorks was current when this manual was produced; newer releases of VxWorks may use revised procedures. -The remote debugging interface (RDB) routines are installed and executed -on the VxWorks target. These routines are included in the VxWorks library -@file{rdb.a} and are incorporated into the system image when source-level -debugging is enabled in the VxWorks configuration. - @kindex INCLUDE_RDB -If you wish, you can define @code{INCLUDE_RDB} in the VxWorks -configuration file @file{configAll.h} to include the RDB interface -routines and spawn the source debugging task @code{tRdbTask} when -VxWorks is booted. For more information on configuring and remaking -VxWorks, see the manufacturer's manual. +To use @value{GDBN} with VxWorks, you must rebuild your VxWorks kernel +to include the remote debugging interface routines in the VxWorks +library @file{rdb.a}. To do this, define @code{INCLUDE_RDB} in the +VxWorks configuration file @file{configAll.h} and rebuild your VxWorks +kernel. The resulting kernel will contain @file{rdb.a} and spawn the +source debugging task @code{tRdbTask} when VxWorks is booted. For more +information on configuring and remaking VxWorks, see the manufacturer's +manual. @c VxWorks, see the @cite{VxWorks Programmer's Guide}. -Once you have included the RDB interface in your VxWorks system image -and set your Unix execution search path to find @value{GDBN}, you are ready -to run @value{GDBN}. From your Unix host, run @code{gdb} (or -@code{vxgdb}, depending on your installation). +Once you have included @file{rdb.a} in your VxWorks system image and set +your Unix execution search path to find @value{GDBN}, you are ready to +run @value{GDBN}. From your Unix host, run @code{gdb} (or @code{vxgdb}, +depending on your installation). @value{GDBN} comes up showing the prompt: |