b133193aa3
This demonstrates that under 64 bit Windows exceptions may not propagate through the kernel code and throwing from inside wxYield() results in either an immediate abort, even if the code calling wxYield() tries to handle the exception, or, even more surprisingly, is just completely ignored. See http://blog.paulbetts.org/index.php/2010/07/20/the-case-of-the-disappearing-onload-exception-user-mode-callback-exceptions-in-x64/ for more information. Moreover, independently of Windows weirdness, throwing from wxYield() also results in a difficult to debug crash when using wxGTK because C++ exceptions can't propagate through C GTK+ code in this case. git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@77465 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 |
||
---|---|---|
.. | ||
except_vc7.vcproj | ||
except_vc8.vcproj | ||
except_vc9.vcproj | ||
except.bkl | ||
except.cpp | ||
makefile.bcc | ||
makefile.gcc | ||
Makefile.in | ||
makefile.unx | ||
makefile.vc |