User`s guide

Remote Debugging 3–5
Building the Executable File
Note: The debug server can only be used to debug already loaded processes;
therefore, the pid option must always be specified. Because the Debug
Monitor is not a multiprocessing system, the process id specified with
this option is ignored.
For example:
%ladebug size.out -rn eb64 -pid 0
This example connects to the server on the node with IP node name eb64 and asks
to debug the process with pid
0. The local object file is called size.out.
3.6 Building the Executable File
To build the executable file for remote debugging, follow these steps:
1. Compile your source files using the -g option. This preserves the symbolic
information in the source files.
2. Link the source files with the -N and -Tx options; where x is the load address for
the executable on the motherboard.
3. Use the CSTRIP utility to strip the coff header from the executable file. Keep the
unstripped executable file.
-rinsist Connects to a running remote process using the connect
insist protocol message instead of the connect protocol
message. This option functions as a request to the server to
connect to the client even if some other client is already
connected. (The previously connected client is
disconnected.) Use only with -rn and -pid.
-rp debug protocol name Specifies the remote debug protocol to be used. The valid
value and default, is ladebug_preemptive.
-rt transport protocol name Specifies the transport protocol to be used for remote debug.
The valid value and default is UDP.
(Sheet 2 of 2)
Command Line Option Description