This content has been marked as final. Show 1 reply
The following might help calify things:
Open the dbx command console: Window->Debugging->DebuggerConsole.
When you press buttons and execute actions in the GUI they are essentially
sent as commands to the dbx command interpreter. You can also just type
So, for (1) verify that you see the next or step commands in the console
and check for any messages emitted by dbx.
Same for (2).
As for (3) I'm not sure I understand. The debugger is usually either waiting for a user action,
as evidenced by the presence of a dbx prompt, or waiting for some event in the debuggee. In the former
case the debugger is stopped. In the latter case it's the debuggee that needs to be stopped and
that is accomplished using the Pause button. Alternatively a ^C in the DebuggerConsole should
also do it.