Closed syamajala closed 11 months ago
What was the commit hash for this? The line numbers don't match anything obvious.
I believe it was:
commit 13cb4852e519f58b910a824674c157959dcb43e8 (HEAD)
Author: Mike <mebauer@cs.stanford.edu>
Date: Fri Nov 3 01:35:34 2023 -0700
legion: disable dumb compiler warnings that do not understand what they are talking about, compiler writers need to get off their butts and write a proper context-sensitive static analysis if they want to do crap like this
But I'm not 100% sure because I seemed to have misplaced the logs from this crash.
The line numbers seem slightly better, but that would mean the stack is not aligned or got smashed or something.
What is the signal for this error? Can you also dumb the assembly of the few instructions around the instruction that crashed? If possible also print the values of num_timeouts
and &key.first
in frame 8.
I have not been able to reproduce this again and am seeing the issue reported in #1595 instead. If I see this again I will reopen this issue.
I am occasionally seeing seg faults in S3D on Frontier.
Here is what I see in the stack traces: