UnmappedAddressException walking stacks in serviceability/sa/ClhsdbPstack.java#core

I've seen this several times with Graal execution of this test.

hsdb> + pstack -v
Error: sun.jvm.hotspot.debugger.UnmappedAddressException: 60001aeeb714
sun.jvm.hotspot.debugger.UnmappedAddressException: 60001aeeb714
at jdk.hotspot.agent/sun.jvm.hotspot.debugger.PageCache.checkPage(PageCache.java:208)
at jdk.hotspot.agent/sun.jvm.hotspot.debugger.PageCache.getInt(PageCache.java:96)
at jdk.hotspot.agent/sun.jvm.hotspot.debugger.DebuggerBase.readCInteger(DebuggerBase.java:355)
at jdk.hotspot.agent/sun.jvm.hotspot.debugger.bsd.BsdAddress.getCIntegerAt(BsdAddress.java:68)
at jdk.hotspot.agent/sun.jvm.hotspot.types.basic.BasicField.getCInteger(BasicField.java:162)
at jdk.hotspot.agent/sun.jvm.hotspot.types.basic.BasicCIntegerField.getValue(BasicCIntegerField.java:54)
at jdk.hotspot.agent/sun.jvm.hotspot.runtime.ThreadsList.length(Threads.java:67)
at jdk.hotspot.agent/sun.jvm.hotspot.runtime.Threads.getNumberOfThreads(Threads.java:187)
at jdk.hotspot.agent/sun.jvm.hotspot.tools.PStack.initJFrameCache(PStack.java:225)
at jdk.hotspot.agent/sun.jvm.hotspot.tools.PStack.run(PStack.java:73)
at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor$32.doit(CommandProcessor.java:1211)
at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor.executeCommand(CommandProcessor.java:2212)
at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor.executeCommand(CommandProcessor.java:2182)
at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor.run(CommandProcessor.java:2053)
at jdk.hotspot.agent/sun.jvm.hotspot.CLHSDB.run(CLHSDB.java:112)
at jdk.hotspot.agent/sun.jvm.hotspot.CLHSDB.main(CLHSDB.java:44)
at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.runCLHSDB(SALauncher.java:281)
at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.main(SALauncher.java:500)

Looking at the hs_err Thread SMR information it appears to be reading at the correct address.

Threads class SMR info:
_java_thread_list=0x000060001aeeb710, length=11, elements={
0x000000014c808210, 0x000000014c834610, 0x000000014c831a10, 0x000000014c832210,
0x000000014c832a10, 0x000000014c83a610, 0x000000014c83ae10, 0x000000012b008210,
0x000000014c023c10, 0x000000014c037410, 0x000000014c928210
}

Opening the core file using lldb also says the address doesn't exist.

(lldb) x 0x000060009aeeb710
error: core file does not contain 0x60009aeeb710

and direct examination of the core file contents using otool -l also shows that the core doesn't contain data for that address.

      cmd LC_SEGMENT_64
  cmdsize 72
  segname
   vmaddr 0x0000600018000000
   vmsize 0x0000000008000000
  fileoff 4465328128 (past end of file)
 filesize 0 (past end of file)
  maxprot 0x00000007
 initprot 0x00000003
   nsects 0
    flags 0x0

This is only occurring on macosx-aarch64-debug so it seem like some kind of core dumping problem. I'm not sure there's anything to be done about it but I wanted a bug to track the problem for triaging.