ASSERT and Windows XP Problem

[Justin Cooke]

Does anyone know how to begin the code trace when a debug assertion fails under Windows XP Home? Under Win 98, if I ran my app in Debug build from the red exlamation point and an assertion failed, I got the popup dialog asking me to 'Abort', 'Retry', or 'Ignore.' If I pressed 'Retry', I was taken to the debug view where I could trace my code, watch variables, etc... Now, under Win XP, the same dialog pops up, but if I click 'Retry', another dialog pops up telling me to press 'Cancel' to debug. If I do this, I get another dialog saying press 'OK' to terminate. I have no way of entering the debug view live. Any help would be greatly appreciated as I've searched all over MSDN to no avial. I'm running: VS 6.0 with SP5 Win XP Home Thanks

[Bugra Barin]

The red exclamation point icon "Executes" your app and won't attach the debugger. So clicking Retry on an assertion dialog won't get you into the debugger because it's not attached. I don't understand how you did it in Win 98 before. And I don't think this issue is OS dependent.

[Justin Cooke]

Thanks for the response. I'm not sure why, but "Executing" the app under Win 98 did allow for the "Retry" debugging. When I got a new computer with XP Home installed, I reinstalled VS 6.0 and SP5 just as I had under Win 98 and the only difference I noticed in VS was the inability to get into the debugger from "Execute." Thanks to another response, I now know I can just use the "Go" command instead and that works fine. Thanks again.