Visual Studio Debugger Breakpoint Helper
No executable code is currently loaded at this location / Symbols Loaded
Symbols loaded for the module, but the breakpoint still didn't bind for some reason. Possible reasons include:
- If the optimizer has done a really great job on your code then it may well have mixed your lines of code around, merged
them together with other lines, or removed them entirely. The debugger will try and slide the breakpoint up to ten
lines down in an effort to find some real code. To see if the optimizer is the reason, try moving the breakpoint to the
beginning of the function. That will always exist, unless the entire function has been removed by the optimizer.
Make sure the code at the breakpoint really is being executed. A simple way is to add a call to MessageBox or similar.
If the dialog doesnt appear, then the code isnt really being run. If the dialog appears but still the breakpoint doesn't hit,
then Break All and check the callstack to try see why the breakpoint is failing.
Breakpoint Helper Has Finished
Did this solve your problem? Yes or No
Click here to start the breakpoint helper again.
©2004 Microsoft Corporation. All rights reserved.
This is a prototype, please send general feedback