ChorusOS man pages section 1CC: Host and Target Utilities

rdbc(1CC)

NAME

rdbc- ChorusOS remote application debugging daemon

SYNOPSIS

rdbc

udp-port

udp-back-port

FEATURES

POSIX_SOCKETS

TIMER

OPTIONS

The following options are supported:

-c: Close the terminal from which rdbc was started. This option disconnects from the host if rdbc is run using rsh.
-h: Print the help and exit.
-l filename: Redirect the rdbc output and the output of the debugged process to a file/device filename and close the original terminal from which rdbc was started.

DESCRIPTION

rdbc is a target utility that provides debugging support for processes.

The rdbc daemon processes remote debugging requests issued by the GDB debugger for ChorusOS systems. It is accessed from a host using Sun RPC over UDP/IP. rdbc must run on a ChorusOS system which includes at least the POSIX_SOCKETS and TIMER features (minimal process and I/O managers).

To enable remote process debugging (if rdbc is not yet running on the target), launch rdbc before any remote debugging session, as follows:

rsh targetname arun rdbc

The rdbc daemon can be killed using the aps and akill C_INIT(1M) commands.

It is possible to run several copies of rdbc in parallel. Different udp-port and udp-back-port values must be used for each copy. The default values are 2072 and 2074. The selected value of udp-port must be provided to GDB in the following command:

target chorusrdb targetname[:udp-port]

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Interface Stability	Evolving

RESTRICTIONS

When a debugged process has been started from the debugging tool, the standard input/output of the debugged application is that inherited from the rdbc daemon. If this is not what you require, start the application using rsh, passing the -d -D options to arun, then attach from the debugging tool. An alternative method is to use a separate copy of rdbc to debug the application.

ChorusOS 5.0 Last Revised December 2001