Configuring and Using RDBD

The RDBD daemon enables the GDB debugging tool to debug core dumps. It is possible to run several RDBD servers on the same host, provided that each one uses a different communication slot number. The slot number must be used as a port number when configuring the debugging tool to use the debug server.

When you start RDBD, you must specify the exact path to the ChorusOS core dump directory manually, as follows:

$  rdbd [options] core_directory

The following options are available:

-fast-start

Do not check for another RDBD daemon already using the selected communication slot. This significantly accelerates startup.

-force-slot

If another RDBD daemon is already using a given slot, force the new RDBD daemon to steal the slot.

-slot number

Creates a communication slot number instead of using the default 0.

core_directory

Directory containing the core files generated by pdump or generated due to an exception.

RDBD can be run in the background because it does not require access to a terminal.