Comment by anitil
18 hours ago
The article mentions that you typically have to longjmp within the same function as setjump (or a descendant function) otherwise your stack gets cleared and you longjmp to a garbage stack. I believe this counts as memory safety? Though I don't quite understand your comment about sigaction, so maybe there's some context I'm missing.
Edit: The extra context- https://usenix.org/legacy/publications/library/proceedings/u...
You don’t have to be in the same function as the setkom; you just have to be in a frame that’s deeper in the stack, or the same frame
The point about memory safety is really this: if I allowed you to longjmp but did not guard it adequately then you could escape the Fil-C capability model, and then all of Fil-C’s bets would be off. I can’t have that ;-)