26 Sep
2011
26 Sep
'11
9:05 a.m.
Yes. The implementation I'm suggesting jumps into a function that hasn't exited yet. In short, we dump a memory image of the process including the stack and the jump buffer. The jump back is done into one of the predecessors of the image dump function, so the function has not exited yet.
The relevant local variables are marked as volatile and are therefore clearly defined.
boost.context implements the functionality of ucontext_t (using assembler for several archtiectures). I'm preparing the lib for the next mini-review. Maybe it could fit your requirements too. Oliver