Unwanted break points

Hi,
I have an application which uses COM componennts. When I debug my application(Release Mode - With Debug Info), the application flow breaks(stops) at various points somewhere inside system DLL and every time I have to press F5(Go). I haven't set these break point, I don't know why they are present. But I have noticed one thing, whenever these break points reaches, in the output(debug) window the following message prints :
HEAP[MyApp.exe]: Invalid Address specified to RtlFreeHeap( 140000, 2d62ef8 )

Anyone know the reason..

Thank you
Prashanth

Mysterious things always happen when you debug release builds, read the article in the DEBUG section on codeguru.com.

Also, make sure you change all your ASSERT(..) to VERIFY(..)

regards
j..

Hi,
Yeah ! I have gone through that section. But in this case I am not facing any problem in release build. It works perfectly fine. Only thing is suddenly some internal break point creeps in (as explained) and I have to press F5 again and again to proceed further.
thanks anyway
Prashanth

I have seen the case where the PDB (debug info) file can get out of synch with the code/application and when you set a breakpoint, the execution will stop somewhere else. I would suggest disabling ALL break points and see if your prog still stops.

I have had this problem on NT where it continually breaks in the kernel DLL with a 'user breakpoint'. I haven't found a cause, but sometimes a full rebuild fixes it.

Dave

Hi,
PDB get out of sync, if your release mode build has optimization settings. If optimization is disabled in Release mode, and the app is rebuild both will synchronize properly. This is just an info.
As you suggested to remove all break points in my code, I did so. Actually debugging is breaking inside system DLL and not inside my DLL.
regards
Prashanth

hi,
yeah I am developing on NT. As you sai, the dialog that pops up say 'User Breakpoint'. Rebuild doesn't solve the problem in my case.
thanks
prashanth

ah, user-breakpoint is different..
I've seen something like this before, and it was usually to do with invalid parameter or something like that