On Tue, 27 Oct 2026 22:01:59 GMT, Chris Plummer <[email protected]> wrote:
>> @plummercj I'm worried that SA core processing on macOS is not working >> correctly. I see this when trying to run `jhsdb jstack` on a core file in >> our own failure handler: >> >> >> Attaching to core >> /System/Volumes/Data/mesos/work_dir/slaves/d28389fb-2d7d-4a3b-8000-f244ff6c0373-S23257/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/c270cd3d-58e1-47a6-812c-cb63928b4b57/runs/df5f7250-f45e-4af7-bb6c-577471329cd0/testoutput/test-support/jtreg_closed_test_hotspot_jtreg_runtime_classFileParser_GiantLineNumberTablesTest_java/runtime/classFileParser/GiantLineNumberTablesTest/core.73670 >> from executable >> /System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-28-cpu+1-134/macosx-aarch64-debug.jdk/jdk-28/fastdebug/bin/java, >> please wait... >> libsaproc ERROR: can't read shared archive path value (0x10907af10) >> (0xa2f003990) >> libsaproc ERROR: failed to workaround class sharing >> Error attaching to core file: Can't attach to the core file. For more >> information, export LIBSAPROC_DEBUG=1 and try again. >> sun.jvm.hotspot.debugger.DebuggerException: Can't attach to the core file. >> For more information, export LIBSAPROC_DEBUG=1 and try again. >> at >> jdk.hotspot.agent/sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal.attach0(Native >> Method) >> at >> jdk.hotspot.agent/sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal.attach(BsdDebuggerLocal.java:282) >> at >> jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.attachDebugger(HotSpotAgent.java:639) >> at >> jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.setupDebuggerDarwin(HotSpotAgent.java:625) >> at >> jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.setupDebugger(HotSpotAgent.java:379) >> at >> jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.go(HotSpotAgent.java:344) >> at >> jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.attach(HotSpotAgent.java:158) >> at jdk.hotspot.agent/sun.jvm.hotspot.tools.Tool.start(Tool.java:209) >> at jdk.hotspot.agent/sun.jvm.hotspot.tools.Tool.execute(Tool.java:134) >> at >> jdk.hotspot.agent/sun.jvm.hotspot.tools.JStack.runWithArgs(JStack.java:90) >> at >> jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.runJSTACK(SALauncher.java:306) >> at >> jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.main(SALauncher.java:507) > > @dholmes-ora Is there an hs_error file that tells you were the CDS archive is > mapped? if yes, are either of the addresses in the following message in the > CDS mapped area?d if yes, can you debug the core file with lldb and see if > that address exists in the core file? > > libsaproc ERROR: can't read shared archive path value (0x10907af10) > (0xa2f003990) @plummercj no there is no hs_err file. The core is created by the tool not by a crash. (I also cannot do any debugging with lldb as I do not have a mac :) ). ------------- PR Comment: https://git.openjdk.org/jdk/pull/33523#issuecomment-6454844410
