Jump to content

DBG N AsyncStop: Difference between revisions

From EDM2
Created page with "Debug Notification -11 - Asynchronous Stop Notification This notification returns: * Cmd= DBG_N_AsyncStop * Value= 0 * Addr= 0 An Asynchronous Stop request has been det..."
 
Ak120 (talk | contribs)
m Redirected page to Debug Notifications
 
Line 1: Line 1:
Debug Notification -11 - Asynchronous Stop Notification
#REDIRECT[[Debug Notifications]]
 
This notification returns:
* Cmd= DBG_N_AsyncStop
* Value= 0
* Addr= 0
 
An Asynchronous Stop request has been detected.
 
The asynchronous stop command is used to get the attention of some debuggee thread, so that the debugger can again control the process. Because any notification results in the debuggee's coming under control of the debugger again, the asynchronous stop notification becomes redundant in that case, and is not returned.
 
The asynchronous stop request will be overridden and ignored if another notification can be performed instead, at the same time. An asynchronous stop notification never becomes a "pending" notification, in the sense that a library load notification becomes pending.
 
[[Category:DBG_N]]
{{DISPLAYTITLE:DBG_N_AsyncStop}}

Latest revision as of 13:27, 10 March 2020