-
Notifications
You must be signed in to change notification settings - Fork 722
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
TestJlmRemoteMemoryAuth_0_FAILED omrport.359 * ** ASSERTION FAILED ** at omr/port/common/omrmemtag.c:145: ((memoryCorruptionDetected)) #16544
Comments
lldb gives me a list of threads. I'm not sure how to find the one associated with the current thread above. The tid doesn't seem helpful. @knn-k do you know? By dumping them all I found #41 is the thread that found the memory corruption. Not all the frames are shown, I suspect the dSYM dirs aren't being found. Do you know how to fix that? All the files are in
|
corruptedMemoryBlock = !j9x 0x0000600003E1E9B0
|
@knn-k are you able to take a look? See my comments in #16544 (comment) |
I don't know what lldb prints as tid. There is no field in the related macOS structs for storing the thread ID as far as I know.
I'm afraid I don't know it, either. I looked into the core file of the failure, but I haven't got any clue. |
Failure link
From an internal build(
mac12x64rt13
):Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
aqa-tests/TKG/output_16733873544924/TestJlmRemoteMemoryAuth_0/20230110-172859-TestJlmRemoteMemoryAuth/results/7.LT2.stderr
30x internal grinder - all passed
The text was updated successfully, but these errors were encountered: