Home > Software engineering >  In the Call Stack debug how area from the current tracking error function step by step up
In the Call Stack debug how area from the current tracking error function step by step up

Time:12-02

On the Internet to check how to solve the problem of an assertion fails, but find out to see don't understand, the following is what I don't understand,

Click the debug menu bar - & gt; Windows - & gt; The Call Stack
In the Call Stack will debug area from the current tracking error function step by step up, until the mian (), __tmainCRTStartup (), mainCRTStartup (), and kernel32. DLL, and then the function in their program will be followed by the main () function,

"In the Call Stack in a above debug area will be from the current tracking error function step by step up" this sentence, how to do?

CodePudding user response:

Double-click the function in the call stack, there will be orientation to the code

CodePudding user response:



Which is the source of the error?

CodePudding user response:

From the post of to be that of DrawItem ASEERT assertion error of
Estimation is button into the selected custom painting, but ever since the draw entity code, should deal with custom painting from CButton derived a new class,

CodePudding user response:

Not you are in the dialog box resource editor window, a Button control attributes set to the OWNER the DRAW, but there is no overloading CButton: : DrawItem virtual function?

CodePudding user response:

Baidu, what all say up step by step to find problems, however, did not know how to upgrade, if there are software had this option at the next higher level

CodePudding user response:

Don't add CButton: : DrawItem
  • Related