Ichthyostega
aac9ee2934
...this bug was spotted as the test failed reproducibly when built with `-fstack-protector-strong` — which adds additional "canary" markers to some kinds of problematic stack storage; this seemed to have the effect that now the second test uses exactly the same location as the preceding test, and thus finds valid data in the newly created work buffers. There is no reason for using uninitialised storage in this test (I can recall that I wanted to build a generic helper and intended to use that as ''virtual overlay'' over existing memory — but that usage never took place, and the `struct Buffer` is not a general-purpose tool now, but only made for this specific test. Thus memory can be easily zero-initialised. |
||
|---|---|---|
| .. | ||
| asset | ||
| control | ||
| engine | ||
| fixture | ||
| mobject | ||
| play | ||
| render-segment-test.cpp | ||