Closed elliottslaughter closed 7 months ago
Keeping in mind the fact that this one crashes, the Legion Spy logs that I am able to generate pass logical and physical verification. Attached here:
This isn't a bug in the physical analysis (which is why Legion Spy is fine). This is (yet another) issue with virtual mappings. Fixing it will take a bit of work, but I at least understand it. If you turn off virtual mappings in the mapper then it should go away completely.
Ok, I have confirmed that this one goes away if I modify the fuzzer not to use any virtual mappings.
Worked around via https://github.com/StanfordLegion/fuzzer/commit/3d77d6c97241517056e1e05bb0ab46ff41a82c1e.
I will keep this issue open as there is an underlying Legion bug here, even if I can work around to avoid it.
Will be fixed with this: https://gitlab.com/StanfordLegion/legion/-/merge_requests/1191
Note this will make virtual mapping initialization for read-only and reduction-only privileges considerably more expensive than they were before but it is necessary for correctness. (Although not as expensive as virtual mappings for read-write privileges which is easily another order of magnitude worse.)
Confirmed the fix with the original reproducer.
Fixed with the merge request above.
My new fuzzer is hitting an assertion. Note the failure is nondeterministic despite the fact that the fuzzer itself is deterministic and I am running in debug mode with
-lg:inorder
:Backtrace:
The trace that generates the assertion is quite short:
If you want to reproduce, you must run exactly the command line above, and use this exact commit of the fuzzer: https://github.com/StanfordLegion/fuzzer/commit/f8cf28f6450f1cdd2172f8170774653a2c3faf11
I'm on my Mac but in theory it should be possible to reproduce this anywhere.