-
Notifications
You must be signed in to change notification settings - Fork 721
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JDK21 serviceability_jvmti_j9_0_FAILED serviceability/jvmti/vthread/BreakpointInYieldTest/BreakpointInYieldTest.java Segmentation error vmState=0x0002000f #18088
Comments
JDK21 aarch64_mac/ milestone 0(
|
@gacholio can you please take a look at this test_output |
The tar file appears to be corrupt
|
Looks like http download corrupts it - fetching with curl now. |
A link to a closely matching JDK11 xa64 build would be helpful (for DDR). The SDK which produced the cores may also help, though I've never been able to run openj9 on my mac (millions of permission errors). |
I think this was actually an x86 mac build. |
Are you talking about the original failure? or the one Jason posted 2 weeks ago? |
I was looking at the start of the PR description. If the cores I have are from amac, the SDK won't help me anyway. I'll see if I can figure anything out from DDR. I also notice that no native stack traces appear in the javacore, which is unhelpful. |
Here is the link for the core in the original failure: https://na-public.artifactory.swg-devops.com/artifactory/sys-rt-generic-local/hyc-runtimes-jenkins.swg-devops.com/hyc-runtimes-jenkins.swg-devops.com/Test_openjdk21_j9_extended.openjdk_x86-64_mac_Personal/27/openjdk_test_output.tar.gz Here is the link to the mac x86 build: https://na-public.artifactory.swg-devops.com/ui/native/sys-rt-generic-local/hyc-runtimes-jenkins.swg-devops.com/Build_JDK21_x86-64_mac_Personal/50/ I think the original failure was found in a personal build @JasonFengJ9 can confirm. But using DDR on a newer JDK on xa64 should work |
It's a crash in GC, so the native stacks probably aren't going to be very informative anyway. |
@tajila yes, the failure was from a personal build before JDK21 nightly/weekly builds run regularly. |
The mac x86 link above doesn't work (it's not even a link to a file!). Even signed in, it just presents me with thousands of unrelated artifacts. |
You need to open it twice, it doesn't work the first time. |
That worked, but what I really want is the linux x86-64 build. This looks like the right place to look: but it hasn't been updated in years. Where should I be looking for the latest builds? |
The latest nightly build is https://na-public.artifactory.swg-devops.com/artifactory/sys-rt-generic-local/hyc-runtimes-jenkins.swg-devops.com/build-scripts/jobs/jdk11u/jdk11u-linux-x64-openj9/877/ibm-semeru-open-jdk_x64_linux_JDK11U_2023-10-10-22-01.tar.gz and you can truncate that to find older nightly builds. However they may not all be head stream builds. |
Thanks, the mac x86 build is also working for me, now trying to get the original core downloaded (keeps failing half way through). |
I have the original failure. Not surprisingly, the stack being walked appears to be in an unmounted continuation. |
The DDR stack extensions don't appear to work on these stacks:
Why DDR needs to know the OS thread ID is a mystery to me, but it's clear we don't fill that in for the stack-allocated threads used to drive the stack walker for unmounted continuations. |
As the continuation is unmounted, the only way to find the failing stack is to examine every continuation using the new extension. @babsingh Is there a command to list all of the continuations? I don't see anything obvious in the DDR help. |
@babsingh Is there a command to list all of the continuations? I don't see anything obvious in the DDR help. It will show in
|
|
These cmds are only available in jdmpview for JDK21+. @fengxue-IS, fyi, if there is an actual bug. |
Through openj9/runtime/jvmti/jvmtiThread.c Lines 1410 to 1413 in 20cb61e
|
Thanks, I'll prototype a fix for this. |
|
The breakpoint handling code was only fixing stacks actively running on a thread. The stacks for continuations also need to be fixed. Fixes: eclipse-openj9#18088 Signed-off-by: Graham Chapman <graham_chapman@ca.ibm.com>
Failure link
From an internal build(
osxrt1
):Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
50x serviceability_jvmti_j9_0 internal grinder - reproduced 7/50
This seems similar to
FYI @babsingh
The text was updated successfully, but these errors were encountered: