The 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.