Unhandled exception: User breakpoint

Hi,

If I run the .exe of a program I made it gives the usual message box "program x has encountered a problem ... "
However, when I run VC++.NET debugger to find out what's wrong, it just works! And then, when I close the program I get

Code:

---

"Unhandled exception at 0x77f7f570 in x.exe: User breakpoint."

---

and the debugger breaks to free.c

I guess I'm doing something that causes access violation, which is, for some reason, isn't detected by the debugger, and then when I shut down, some destructor calling delete causes the above error message.

My questions:

1. is the above error message really caused by deleting some memory not allocated by new (or free)?

2. Why isn't the first error message detected by the debugger?

3. how am I supposed to debug this if the debugger doesn't detect it (is there a better way to do debugging)?

thanks in advance.

Post your code.

I think I may know where this problem lies. Often, you can accidentally muck around with memory that isn't yours. When it comes time to close the program, it has a bit of trouble and throws a wobbly. But really, I couldn't say for sure unless I had THE CODE in front of me.

In addition, what does the call stack say when the error occurs? If you look up (or down I guess) the call stack, you should be able to see what part of your code is being destroyed that is calling free. That would help you narrow down which memory might be getting overwritten, or if an object is being deleted twice, etc.

Also, I don't know if you use exceptions, but sometimes it is helpful to change all of your Exception settings to "stop always". If an exception or access violation occurs in the middle of the program, it will break execution and you can look into your call stack and see exactly where in your code it occurred.

thank you guys sooo much, this call satck thingy is exactly what I needed, I wasn't aware of it before btw :) :)
it turned out that I forgot to overload = operator in one of my classes, which contained a pointer to the beginning of an array, when I used = to copy an instance fields to another's, I was actually copying a memory address instead of data, later when the program exits, the destructor is called, deleting one instance and leaving the other instance field pointing to memory which isn't mine any more :p
I just overloaded the = operator to copy data instead of addresses, I don't see that dreaded error message any more :D
thanks again.

PS: as for posting the code, it's not just one small file to post, and I didn't know where that error was actually happening, all what I got was free.c, now with call stack I can locate errors in no time.

I've got another problem to fix, I'll try on my own, if I can't manage to fix it, I'll create a new thread, but any way, does anybody know why glTexParameteri causes access violation? it's called exactly after gluBuild2DMipmaps, I guess it has something to do with my image loading code, it only happens with some images not all of them, JPG images, I noticed that it happens with none 2^i x 2^j images.
I'll try to fix it, otherwise I'll post in the game programming forum.

^^