| Previous | Next |
| DBG_NO_STATE_CHANGE | RPC_NT_INVALID_STRING_BINDING |
DBG_APP_NOT_IDLE
The target was not in the idle state required by the debugger
Some debugger operations require the target to have no outstanding transition or command activity. This status means that condition was not met. A thread may still be running, an event may await continuation, or command processing may still be in progress.
It is a debugger coordination error, not a measurement of user-interface responsiveness or CPU utilization. Diagnosis requires the debugger state machine and outstanding events, not Task Manager idle percentages.
What to inspect
- List all stopped and running target threads and any event awaiting ContinueDebugEvent.
- Check for asynchronous debugger commands that have not completed.
- Confirm that process attach, detach, and termination transitions are not overlapping.
- Wait for or cancel the owning operation rather than forcing a second state-changing command.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: debugging events
- Microsoft: writing the debugger main loop
- Wine source: debugger API implementation
Looking for a different code? Search another status or error code.