Code:
In the InitInstance function, create the dialog object,
Then call DoModal dialog object function,
Operation mode:
1: Ctrl + F5, began to perform, no debug mode, the program is running normal,
2: F5, start debugging, program crashes, after the interruption, breakpoint to DLG. DoModal function, function stack information, see figure,
3: will mfc140ud. DLL is copied to the program directory, all operations are normal boot program
CodePudding user response:
Collapsed in the pop-up dialog box, press the corresponding button to enter debugging press Alt + 7 key to view the Call Stack, namely "the Call Stack" from the inside to the following out of from the inner to outer function Call history, double-click a row to the cursor to the Call of the source code or assembly instruction, don't understand when double click on the next line, until we can read ,https://www.baidu.com/s? Wd=mfc140ud
CodePudding user response:
The problem of suspected MFC140UD. DLL can't load,I released out version, MFC140UD. DLL in the program directory and run the program sometimes will collapse (change the program name, or path name), the stack and the DUMP file,
CodePudding user response:
Perhaps because ofIn the InitInstance function,
Don't should
Create dialog object,
Then call DoModal dialog object function,
Baidu search relevant keywords,
CodePudding user response:
The