F12 and Visual Studio
Tim Hutton
tim.hutton at gmail.com
Wed Jun 6 06:02:06 PDT 2007
Hello,
When debugging a wxWidgets project in Microsoft Visual Studio, hitting
F12 causes an unhandled exception:
"Unhandled exception at 0x7c901230 in llama.exe: User breakpoint."
The call stack is just ntdll.dll, similar to that described here:
http://blogs.msdn.com/greggm/archive/2004/04/16/114893.aspx
So it looks like heap corruption.
It seems to happen on all wxWidgets projects (I've tried my own and
some samples). It happened in 2.8.3 and still in 2.8.4. I'm using MSVC
7 (2003) on Win XP.
Nothing bad happens when executing the exe (Debug or Release), only
when debugging (Debug or Release). Effectively it means I can't use
F12 as an accelerator key, which is a pain.
Any ideas?
I wondered whether it was related to this F12 issue:
http://burnout.geo.umn.edu/EnvImg/binCache/49_wxVisualSetup%20Readme.htm
but changing the MSVC key bindings didn't make any difference.
There's a function-key bug reported here:
http://sourceforge.net/tracker/index.php?func=detail&aid=1620758&group_id=9863&atid=109863
but probably not related since the problem happens even if F12 isn't
being used as an accelerator.
None of the other function keys cause a problem. And Ctrl-, Shift- or
Alt-F12 don't cause a problem, only F12 itself.
Thanks,
Tim
More information about the wx-users
mailing list