The recent upgrade from VS2003 to VS2010 means that we are now using a C runtime where invalid parameters cause the runtime to trap to an "invalid parameter handler", see:
http://msdn.microsoft.com/en-us/library/ksazx244.aspx
This RFE proposes that we examine this to see whether it would make sense for HotSpot to install its own handler that use the existing fatal error mechanism.
6983520 is an example where a behavior change in the C runtime resulted in a crash/exception-popup without any fatal error log.
http://msdn.microsoft.com/en-us/library/ksazx244.aspx
This RFE proposes that we examine this to see whether it would make sense for HotSpot to install its own handler that use the existing fatal error mechanism.
6983520 is an example where a behavior change in the C runtime resulted in a crash/exception-popup without any fatal error log.
- relates to
-
JDK-6983520 java/io/pathNames/GeneralWin32.java fails with jdk7-b108 (win)
-
- Closed
-