3 ms·
When you start stack-swapping, at some point you're going to need to deal with unwinding the stack (exceptions). What surprises me is that they said that, in m
by twhitmore 7y ago
When you start stack-swapping, at some point you're going to need to deal with unwinding the stack (exceptions).
What surprises me is that they said that, in most cases, throwing exceptions seemed to work OK!
I would have assumed that if it wasn't properly supported by the Boost Context object, it would have frequently been corrupting memory. Maybe they just never noticed the corruption.
- AstralStorm 7y agoThe instant they told about null registers I though "someone has corrupted the stack". From there enabling ASAN or perhaps even stack-protector (even in Release) should've caught it rather quick... (First context switch, likely resume with exception raised.) Now seeing a crash in exception handler, that is something. It's rather sad they didn't fix Boost.Context, seems like it could always use more platform ifdefs.