[jdk11u-dev] RFR: 8293563: [macos-aarch64] SA core file tests failing with sun.jvm.hotspot.oops.UnknownOopException [v2]

[Christoph Langer]

On Mon, 6 May 2024 10:04:06 GMT, Andrew Haley <aph at openjdk.org> wrote:

> The last time I tried, I couldn't get core files at all without doing a ton of fiddly config, turning off SIP, etc. Did you have to do any of that? Perhaps it's no longer a problem.

Hm, when current jdk11u-dev hits our ci, the MacOS arm64 test is failing with exceptions like:

sun.jvm.hotspot.oops.UnknownOopException
	at jdk.hotspot.agent/sun.jvm.hotspot.oops.ObjectHeap.newOop(ObjectHeap.java:266)
	at jdk.hotspot.agent/sun.jvm.hotspot.runtime.JavaThread.getThreadObj(JavaThread.java:359)
	at jdk.hotspot.agent/sun.jvm.hotspot.runtime.JavaThread.getCurrentParkBlocker(JavaThread.java:411)
	at jdk.hotspot.agent/sun.jvm.hotspot.runtime.DeadlockDetector.print(DeadlockDetector.java:82)
	at jdk.hotspot.agent/sun.jvm.hotspot.runtime.DeadlockDetector.print(DeadlockDetector.java:39)
	at jdk.hotspot.agent/sun.jvm.hotspot.tools.StackTrace.run(StackTrace.java:62)
	at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor$24.doit(CommandProcessor.java:1066)
	at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor.executeCommand(CommandProcessor.java:1974)
	at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor.executeCommand(CommandProcessor.java:1944)
	at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor.run(CommandProcessor.java:1824)
	at jdk.hotspot.agent/sun.jvm.hotspot.CLHSDB.run(CLHSDB.java:99)
	at jdk.hotspot.agent/sun.jvm.hotspot.CLHSDB.main(CLHSDB.java:40)
	at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.runCLHSDB(SALauncher.java:224)
	at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.main(SALauncher.java:522)

And with this modification it goes away. That's all I can say... 😉 

The failing tests are
hotspot / serviceability/sa/ClhsdbFindPC.java#id1
hotspot / serviceability/sa/ClhsdbFindPC.java#id3

-------------

PR Comment: https://git.openjdk.org/jdk11u-dev/pull/2698#issuecomment-2095638229