Browser keep stopping with user breakpoint and opens visual studio 6 in debug mode

Question

Hi,

Following my last question (see: http://stackoverflow.com/questions/1184175/problem-in-hosting-activex-on-vista-in-a-visual-studio-6-c-application) I ran into a strange problem. I hope this’ll be a simpler issue to the experts here:

Each time I run certain application like iexplorer or firefox, the Visual Studio 6 suddenly opens up in debug mode with a message “User breakpoint called from code at 0xSOMETHING”. I can press F5 to continue but the applications run slowly and needless to say I have no wish to debug these applications…

My guess is that when I worked on my VC++ application I placed breakpoints at windows methods like CAxDialogImpl::Create(), AtlAxCreateDialogA() etc’, and for some reason it was kept somewhere.

Of course I now removed all the breakpoints and re-compiled the project but still this keeps happening! I checked in the tools->options but the “Just-in–time debugging” is not marked.

Any idea?

(I use Visual Studio 6 which I installed on Vista)

Thanks a lot, Erik

Answer 1

Not sure this helps but anyways:

Try disbaling the default debugger option. (It says Dr. Watson but it depends what you have set as the default debugger)

http://www.bridgetonova.com/2007/09/how-to-disableenable-windows-default.html

Also as per this post Visual Studio 6 is not supported on Vista. Only Visual Basic is.

http://www.itwriting.com/blog/167-visual-studio-6-on-vista.html

Answer 2

You should probably re-ensure yourself that you have removed all calls to DebugBreak() and manual break-points. Also try to ensure that when you recompile you re-register everything to point to the right places (i.e. the activex pointed to by the guid in the registry is actually the latest recompile).

Answer 3

A comment to the first answer: (I logged in as a user now so I cannot add a regular comment)

Again thank you. I checked Vista rating - score is 3.8. And I didn't see any VS processes. I think it works OK now. A bit slow, but what can you do - that's IE. I guess I'll stick to FireFox (which works fine now)

Cheers, Erez