3 ms·
This bug wasn't caused by a read beyond the current bounds of the stack, but a stale value from a prior call to the same function at the exact same location on
by LegionMammal978 2y ago
This bug wasn't caused by a read beyond the current bounds of the stack, but a stale value from a prior call to the same function at the exact same location on the stack. Buffer-overflow protections like you describe wouldn't help here.
- cadamsdotcom 1y agoI’m not sure - it seems like said function returns before the next call is made. I’m proposing the memory of the fresh stack frame initially reads as zeroes until written to.