Within a few seconds, the testcase usually hits: Assertion failure: Comparator::compare(*minimum, *node) < 0, at SplayTree.h:263 Why is this non-deterministic? Can this kind of bug be made deterministic, perhaps by adding more assertions? (The non-determinism caused me to spend several hours massaging the testcase instead of several minutes simply reducing it.)
Might this have started as a result of the patch to bug 849263? I still think that patch is right, though.
(In reply to David Baron [:dbaron] (don't cc:, use needinfo? instead) from comment #2) > Might this have started as a result of the patch to bug 849263? I still > think that patch is right, though. I believe so, yes. This appears to be a different symptom of bug 850672. Thanks for the testcase Jesse!
Makes sense. The non-determinism might come from [whether and when the presarena reuses a memory address]. This particular SplayTree cares whether frame pointers are reused because its entries are sorted by by depth and then frame pointer.
WFM in local m-c debug build on Linux64 and OSX.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
OS: Mac OS X → All
Hardware: x86_64 → All
Resolution: --- → WORKSFORME
Flags: in-testsuite? → in-testsuite+
Assignee: nobody → jruderman
You need to log in before you can comment on or make changes to this bug.