For a description of the data returned with each notification, select
旼컴컴쩡컴컴컴컴컴컴컴컴컴컫컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 쿙ot. 쿙otification Name 쿏escription � 쿙o. � � � 쳐컴컴탠컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 � 0 �DBG_N_Success 쿞uccessful command completion � 쳐컴컴탠컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 �-1 �DBG_N_Error 쿐rror detected during command � 쳐컴컴탠컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 �-6 �DBG_N_ProcTerm 쿛rocess termination - DosExitList � � � 쿭one � 쳐컴컴탠컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 �-7 �DBG_N_Exception 쿐xception detected � 쳐컴컴탠컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 �-8 �DBG_N_ModuleLoad 쿘odule loaded � 쳐컴컴탠컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 �-9 �DBG_N_CoError 쿎oprocessor not in use error � 쳐컴컴탠컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 �-10 �DBG_N_ThreadTerm 쿟hread termination - not in � � � �DosExitList � 쳐컴컴탠컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 �-11 �DBG_N_AsyncStop 쿌sync Stop detected � 쳐컴컴탠컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 �-12 �DBG_N_NewProc 쿙ew Process started � 쳐컴컴탠컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 �-13 �DBG_N_AliasFree 쿌lias needs to be freed � 쳐컴컴탠컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 �-14 �DBG_N_Watchpoint 쿥atchpoint hit � 쳐컴컴탠컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 �-15 �DBG_N_ThreadCreate 쿟hread creation � 쳐컴컴탠컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 �-16 �DBG_N_ModuleFree 쿘odule freed � 쳐컴컴탠컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 �-17 �DBG_N_RangeStep 쿝ange Step detected � 읕컴컴좔컴컴컴컴컴컴컴컴컴컨컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸
Note: References to "IP" in the data return descriptions refer to the instruction pointer address. This is the 32-bit equivalent of the CS:EIP instruction pointer, regardless of the CS selector. This is also known as a linearized instruction pointer.
Some notifications (such as DBG_N_ModuleLoad and DBG_N_Watchpoint) may require multiple returns to the debugger. These additional pending notifications will be returned before the process being debugged can execute any more user code, and will be returned on the DBG_C_Go, DBG_C_SStep, or DBG_C_Stop commands.
Note that more notifications might be pending at any time, so a debugger should be ready to handle any notification at any time that a DBG_C_Go, DBG_C_SStep, or DBG_C_Stop command is issued.
If DosDebug returns ERROR_INTERRUPT after a command, the next notification might have been lost. If the process being debugged was executing code at that time (via a DBG_C_Go, DBG_C_SStep or DBG_C_RangeStep command), it will be stopped automatically. To prevent this, DosDebug should not be used by thread 1 while signals are being used, or the debugger should issue DosEnterMustComplete before issuing the command.