- Group: added_in_v2.1 --> nice_to_have
A simple request, using Bochs is nice as it is however
the debugger interface should be decoupled from a mere
consol type application. To facilitate a number of
other interfaces to be used for debugging, I suggest
the following:
1: complete GDB complience. This is not terribly hard
just takes time. Perhaps -debugger-gdbonly as a
command line to force this after implementation or make
the default behavior this and --debugger-oldstyle? hmmm
this should also be a configuration switch.
2: Command line switch and or configuration switch for
directing the debugger IO to a port.
3: Choice of debugger startup. IE it starts on boot up.
OR it starts when the program recieves a stop (from
the client).
4: Debugger sanity. If nothing is attached to the
socket (IE no client has connected) output to the
debugger is disabled and so is interactive operation
(the consol is essentially disabled for debugger use).
5: Optional security. Allow local host only
connections, or connections on the same machine (cross
machine interface as an option I think is diserable
especially if the program is a monster). This keeps
unwanted/undesired things from happening while runing
bochs :D
This should allow for a debugger with reasonable
interactive control. that already exists with Bochs.
It also means that a user could say debug an OS or
something loading in an OS that is crashing.. etc.