Jump to content

DBG N ModuleLoad: Difference between revisions

From EDM2
Created page with "Debug Notification -8 - Module Load Notification This notification returns: *Cmd= DBG_N_ModuleLoad *Value= MTE (Module Table Entry) handle of newly attached module *Addr=..."
 
Ak120 (talk | contribs)
Redirected page to Debug Notifications
 
Line 1: Line 1:
Debug Notification -8 - Module Load Notification
#REDIRECT[[Debug Notifications]]
 
This notification returns:
*Cmd= DBG_N_ModuleLoad
*Value= MTE (Module Table Entry) handle of newly attached module
*Addr= 0
 
A module has just been loaded. This occurs either at program startup, or during a call to DosLoadModule.
 
The newly attached module's handle is returned via Value. You can use this handle with DosQueryModuleName, or with the Debug DBG_C_NumToAddr command, for symbolic debugging. A debugger should save these handles for future reference.
 
There may be many module attachments done at one time, but DosDebug is only able to communicate a single load during any one notification. In this case, the additional library load notifications become pending. The debugger should issue repeated DBG_C_Stop commands to be notified of these additional library loads, until Success is returned from the DBG_C_Stop command. If the DBG_C_Go, DBG_C_SStep, or DBG_C_RangeStep commands are issued instead of the DBG_C_Stop command, the pending notifications will be returned immediately, until there are no further notifications.
[[Category:DBG_N]]
{{DISPLAYTITLE:DBG_N_ModuleLoad}}

Latest revision as of 13:50, 10 March 2020