What does this mean?
-
I encounter a warning, when i debug a programe. The warning message is "User breakpoint called from code at 0x77f97704".I donot know the reason. When this warning message appears, VC shows a screen of assembly code to me.Please tell me the reason to cause this warning . I love sea
-
I encounter a warning, when i debug a programe. The warning message is "User breakpoint called from code at 0x77f97704".I donot know the reason. When this warning message appears, VC shows a screen of assembly code to me.Please tell me the reason to cause this warning . I love sea
Is VC stopped at a line that says "int 3"? You've probably hit an assertion somewhere i.e. done something wrong. Bring up the call stack (ALT-7) and have a look at what was going on at the time. If you press F11 a few times, you might be able to switch back to your original source code as well.
he he he. I like it in the kitchen! - Marc Clifton (on taking the heat when being flamed) Awasu v0.4a[^]: A free RSS reader with support for Code Project.
-
Is VC stopped at a line that says "int 3"? You've probably hit an assertion somewhere i.e. done something wrong. Bring up the call stack (ALT-7) and have a look at what was going on at the time. If you press F11 a few times, you might be able to switch back to your original source code as well.
he he he. I like it in the kitchen! - Marc Clifton (on taking the heat when being flamed) Awasu v0.4a[^]: A free RSS reader with support for Code Project.
Yes you are right. But i donot know what the assembly codes mean.Have you ever encourted this problem?How can i solve this problem. I love sea
-
Yes you are right. But i donot know what the assembly codes mean.Have you ever encourted this problem?How can i solve this problem. I love sea
You don't need to understand the assembly. INT 3 is how Visual C++ stops the program if an assertion failure happens. If you don't know what that means, look up what the assert() macro does. What has happened is that some code somewhere has noticed that something has gone wrong and stopped the program for you, where it happened, so that you can do something about it. For example, if you call strlen() like this:
char* p = NULL ; size_t n = strlen(p) ;strlen() might be smart enough to detect that you passed in a NULL pointer and assert. So bring up the call stack as I suggested and you can see exactly where your program was when it stopped. And pressing F11 a few times *might* get out of the assembly code and back to some C source code.
he he he. I like it in the kitchen! - Marc Clifton (on taking the heat when being flamed) Awasu v0.4a[^]: A free RSS reader with support for Code Project.