This is to enable stopping the target just to be able to send it commands.  In these cases, the stop reason set by the IDebugger::stopped_signal would be SIGNAL_RECEIVED_BEFORE_COMMAND.  The handling code would thus avoid querying IDebugger for context upon the stop, b/c it would know that the real intended command is about to follow.

This would allow an interesting feature/simplification that would be, e.g, the ability for the user to set a breakpoint in a running target w/o explicitely having to stop it.  Nemiver would stop the target (avoiding the popup shown when a signal is received), set the breakpoint and just continue.