Added disclaimer (requested by WRS) on how procedures described for
connecting to VxWorks may change in future releases of VxWorks.
This commit is contained in:
parent
d141f3e30d
commit
9941f866a5
1 changed files with 4 additions and 0 deletions
|
@ -323,6 +323,10 @@ the VxWorks shell can also be debugged. _GDBN__ uses code that runs on
|
||||||
both the UNIX host and on the VxWorks target. The program
|
both the UNIX host and on the VxWorks target. The program
|
||||||
@code{_GDBP__} is installed and executed on the UNIX host.
|
@code{_GDBP__} is installed and executed on the UNIX host.
|
||||||
|
|
||||||
|
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
|
The remote debugging interface (RDB) routines are installed and executed
|
||||||
on the VxWorks target. These routines are included in the VxWorks library
|
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
|
@file{rdb.a} and are incorporated into the system image when source-level
|
||||||
|
|
Loading…
Reference in a new issue