-
Bug
-
Resolution: Fixed
-
P4
-
9, 15
-
b02
-
x86
-
windows
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8267436 | 11.0.12 | Thomas Stuefe | P4 | Resolved | Fixed | b04 |
This problem is very similar to
I think conditionally wrapping the call to RUN_ALL_TESTS() in gtestMain.cpp with a __try/__except block using topLevelExceptionFilter will address this problem. For the conditionalization, I suggest using the existing GTEST_HAS_SEH macro.
- backported by
-
JDK-8267436 [Windows] Structured Exception Catcher missing around gtest execution
-
- Resolved
-
- duplicates
-
JDK-8220220 [TESTBUG] [windows] gtests cannot test functionality relying on signal handling (e.g. SafeFetch)
-
- Closed
-
- relates to
-
JDK-8074860 Structured Exception Catcher missing around CreateJavaVM on Windows
-
- Resolved
-
-
JDK-8257828 SafeFetch may crash if invoked in non-JavaThreads
-
- Resolved
-
-
JDK-8264408 test_oopStorage no longer needs to disable some tests on WIN32
-
- Resolved
-
-
JDK-8267138 Stray suffix when starting gtests via GTestWrapper.java
-
- Resolved
-
-
JDK-8348122 Windows: on error, gtest SEH handler is invoked instead of the JVM signal handler
-
- Closed
-