next up previous contents
Next: MOSS system calls Up: Remote debugging Previous: Running applications under the

Features supported by MOSS's remote GDB stub

MOSS supports most of the features of GDB's remote debugging protocol that are applicable to a single-process environment, such as:

The MOSS remote debugging stub currently does not support compression of register state; this would make remote debugging more responsive, because less information would have to be passed across the wire each time the program stops for instructions from the remote debugger.

Also, currently, MOSS will only notify the remote debugger of signals that have SIG_DFL action, i.e. signals that would otherwise cause the program to terminate. There is a trivial change to signal.c that you can make to cause all signals, including signals the program has installed handlers for, to be sent to the remote debugger (and the debugger can send them back again if appropriate). This behavior is not enabled by default because it slows things down considerably when lots of signals are occurring (e.g. if you're servicing lots of hardware interrupts with signals), and the ``feature'' usually only gets in the way anyway. However, if you'd like to turn it on, post a message to the MOSS mailing list and we'll tell you how (or maybe just make it a ``proper'' option...).



Bryan Ford