JDK-8346717 : serviceability/dcmd/vm/SystemDumpMapTest.java failing on Windows with "Stack base not yet set for thread id"
  • Type: Bug
  • Component: core-svc
  • Sub-Component: tools
  • Affected Version: 25
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows
  • Submitted: 2024-12-20
  • Updated: 2025-01-20
  • Resolved: 2025-01-12
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 25
25 b06Fixed
Related Reports
Relates :  
JDK-8340401 - DcmdMBeanPermissionsTest.java and SystemDumpMapTest.java fail with assert(_stack_base != nullptr) failed: Sanity check
Description
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (c:\$DIR\src\hotspot\share\runtime\thread.cpp:150), pid=46324, tid=8868
#  assert(_stack_base != nullptr) failed: Stack base not yet set for thread id:37288 (0 if not set)
#
# JRE version: Java(TM) SE Runtime Environment (25.0+4) (fastdebug build 25-ea+4-LTS-306)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (fastdebug 25-ea+4-LTS-306, mixed mode, sharing, tiered, compressed class ptrs, z gc, windows-amd64)
# Problematic frame:
# V  [jvm.dll+0xfad719]  Thread::stack_base+0x39
#
# Core dump will be written. Default location: C:\$DIR\testoutput\test-support\jtreg_open_test_hotspot_jtreg_hotspot_serviceability\scratch\2\hs_err_pid46324.mdmp
#
# If you would like to submit a bug report, please visit:
#   https://bugreport.java.com/bugreport/crash.jsp
#

Stack: [0x0000001521c00000,0x0000001521d00000],  sp=0x0000001521cfc840,  free space=1010k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V  [jvm.dll+0xfad719]  Thread::stack_base+0x39  (thread.cpp:149)
V  [jvm.dll+0xc86d40]  print_thread_details_for_supposed_stack_address+0x90  (memMapPrinter.cpp:218)
V  [jvm.dll+0xc86b04]  MappingPrintSession::print_nmt_info_for_region+0x1f4  (memMapPrinter.cpp:261)
V  [jvm.dll+0xc8758f]  MemMapPrinter::pd_print_all_mappings+0x4cf  (memMapPrinter_windows.cpp:245)
V  [jvm.dll+0xc8670e]  MemMapPrinter::print_all_mappings+0x7e  (memMapPrinter.cpp:283)
V  [jvm.dll+0x669cce]  SystemDumpMapDCmd::execute+0x7e  (diagnosticCommand.cpp:1191)
V  [jvm.dll+0x66e975]  DCmd::parse_and_execute+0x505  (diagnosticFramework.cpp:416)
V  [jvm.dll+0xc6a36b]  jmm_ExecuteDiagnosticCommand+0x15b  (management.cpp:2077)
C  0x0000013eb708ebc9  (no source info available)
Comments
Changeset: f04a6422 Branch: master Author: Simon Tooke <stooke@openjdk.org> Committer: David Holmes <dholmes@openjdk.org> Date: 2025-01-12 21:39:43 +0000 URL: https://git.openjdk.org/jdk/commit/f04a6422469709d22bd92bf5d00655f741956efd
12-01-2025
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/22870 Date: 2024-12-23 18:43:07 +0000
24-12-2024
This was supposed to be addressed by JDK-8340401 which introduced stack_base_or_null() to be used in these contexts.
21-12-2024