@epilanthanomai It's definitely something foreign to a lot of people, so no shock. I added a local variable in a function and suddenly unrelated code was crashing. I presumed it was a stack depth issue, but needed to confirm it by actually tracking some memory through hours of runs to finally see that, yep indeed, part of the corrupted memory contained the address of a recently called function, a sign that the overwrite was an activation frame.
@epilanthanomai Indeed even for a low-level systems hacker like me, this doesn't typically come up. Either someone's engaged hardware-backed memory protection already or I'm working on hardware so primitive that it doesn't even have a stack.
Signs & Codes is a private Mastodon instance built around a community of friends.