We will identify here possible requirements for the type of debug that may be
provided :
[(R1)]:
We want to use GDB as the front-end debugger,
[(R2)]:
We want to support at least Intel and PowerPC as target processor architecture,
[(R3)]:
We want to use the GDB thread debugging interface,
[(R4)]:
We want to be able to debug a remote target over a serial line,
[(R5)]:
We want to be able to debug a remote target over Ethernet,
[(R6)]:
The set of target code path we will be able to debug using RGDBSD must
be clearly identified. It will be called Debug Path Set (DPS) in the
remaining of this document,
[(R7)]:
DPS must include the RTEMS core executive itself,
[(R8)]:
DPS must include the FreeBSD stack,
[(R9)]:
DPS must include anything but the FreeBSD stack and the RTEMS
core executive,
[(R10)]:
We want to enable several persons to debug different parts of the code
running on the target,
[(R11)]:
As much as possible the system must be frozen during a debug session
so that debugging a particular portion of code does not prevent another part
from functioning,
RTEMS Remote Debugger Server Specifications