Setting up an Application Debugging Session

Application debugging uses the RDBC daemon which processes remote debugging requests issued by the GDB debugging tool. It is accessed from a host using Sun RPC over UDP/IP. RDBC must run on a system which includes at least the POSIX_SOCKETS feature (minimal process and I/O managers).

Configuring and Using RDBC

The RDBC daemon can be started automatically or manually.

For RDBC to be started automatically, the conf/sysadm.ini file, read during system initialization by C_INIT, must contain a command which mounts the NFS root. If this mount command is present, edit the conf/sysadm.ini file and add the following line just after the mount command:

rdbc

You cannot use the & character with this command.

RDBC will follow NFS root changes.

To start RDBC manually, as a normal application, type the following at the command line:

$ rsh target_name rdbc

Running RDBC manually enables you to choose when you want to carry out application debugging, freeing up valuable resources.

To stop RDBC, use the akill command. First identify the process ID (pid):

$ rsh target_name aps

Then kill the RDBC process:

$ rsh target_name akill pid

Your application debug session terminates when you stop RDBC.

The input and output of debugged applications is displayed in the terminal in which you started RDBC. If you start RDBC with the -c option, the terminal connection is closed and RDBC runs in the background.

RDBC can be used to debug several applications at the same time from different GDB clients.

Two or more RDBC servers can be run on the same target to provide a separate console for each program being debugged.

See rdbc(1CC) for more information.

Customers who have the source delivery of ChorusOS 5.0 can find information on how to compile GDB for application debugging in the README.CHORUSOS file, located in install_dir/chorus-family/opt/gdb/doc/.