-
Bug
-
Resolution: Fixed
-
P4
-
14, 15
-
b05
Test runtime/ErrorHandling/ThreadsListHandleInErrorHandlingTest.java
fails to find a pattern
"=>.* JavaThread \"main\" .* _threads_hazard_ptr=0x[0-9A-Fa-f][0-9A-Fa-f]*, _nested_threads_hazard_ptr_cnt=0.*"
Basically it fails because stacktrace was not generated.
Threads class SMR info:
_java_thread_list=0x00007fd7540a4b70, length=11, elements={
0x00007fd7ac022000, 0x00007fd7ac209000, 0x00007fd7ac20b800, 0x00007fd7ac214800,
0x00007fd7ac217800,
[error occurred during error reporting (printing all threads), id 0xb, SIGSEGV (0xb) at pc=0x00007fd7b319370a]
VM state:not at safepoint (normal execution)
fails to find a pattern
"=>.* JavaThread \"main\" .* _threads_hazard_ptr=0x[0-9A-Fa-f][0-9A-Fa-f]*, _nested_threads_hazard_ptr_cnt=0.*"
Basically it fails because stacktrace was not generated.
Threads class SMR info:
_java_thread_list=0x00007fd7540a4b70, length=11, elements={
0x00007fd7ac022000, 0x00007fd7ac209000, 0x00007fd7ac20b800, 0x00007fd7ac214800,
0x00007fd7ac217800,
[error occurred during error reporting (printing all threads), id 0xb, SIGSEGV (0xb) at pc=0x00007fd7b319370a]
VM state:not at safepoint (normal execution)
- duplicates
-
JDK-8193560 Thread-SMR output during VMError reporting can be racy
-
- Closed
-
- is blocked by
-
JDK-8256383 PlatformMutex::try_lock has different semantics on Windows and Posix
-
- Resolved
-
-
JDK-8258284 clean up issues with nested ThreadsListHandles
-
- Resolved
-
- relates to
-
JDK-8258284 clean up issues with nested ThreadsListHandles
-
- Resolved
-
-
JDK-8259397 ThreadsSMRSupport::print_info_on() should use try_lock_without_rank_check()
-
- Resolved
-
(2 links to)