-
Notifications
You must be signed in to change notification settings - Fork 728
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
jsr292Test_JitCount0 memoryCorruptionDetected #20617
Comments
@hzongaro fyi |
Issue Number: 20617 |
I wasn't able to do anything useful with the core file that was produced in gdb. I was able to reproduce the crash in a grinder run, but still couldn't manage to debug in gdb.
I spent some time looking at the core file in jdmpview, but nothing obvious jumped out at me. If failures show up frequently, I'll try to capture further information in a grinder run. |
I assume you are either running gdb on the machine that produced the core or running It's not obvious if you know how to get the corrupted address, fyi if you don't.
|
Thanks, @pshipton! I had missed your comments.
I was running gdb on a different machine, but I had downloaded the jdk and debug images, and pointed gdb to the directories containing them. That usually works for me, but if there are reasons why
Thanks for that tip on getting a corrupted address! I did not know about it. |
That only works if it's the same OS and versions of all the system libraries. Otherwise you need jpackcore to collect the libraries from the crashing machine. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk21_j9_extended.functional_s390x_linux_Nightly_testList_1/358 - rh7-390-2
jsr292Test_JitCount0_0
https://openj9-artifactory.osuosl.org/artifactory/ci-openj9/Test/Test_openjdk21_j9_extended.functional_s390x_linux_Nightly_testList_1/358/functional_test_output.tar.gz
The text was updated successfully, but these errors were encountered: