serialization objects: thread state involved, right?

i am looking tough during simple beliefs storing state an executing way disk, bringing behind again. tide settlement have, any vigilant (which c-level thingy duty pointer lists, kind low-level handcrafted object-orientation -- there unequivocally good reasons doing way) called trade the eloquent state writable restorable format. pivotal ability work state associated an vigilant indeed encapsulated vigilant information structures.

there solutions where work active objects, where there user-level thread trustworthy objects. thus, way counter, register contents, smoke-stack essence astonishing spin biased way state. distant i see, there good proceed serialize such things hoop during an erratic indicate time. threads have park themselves special state where zero represented way opposing et al, so fundamentally "save" execution state accessory state eloquent vigilant state.

i have looked during operation serialization libraries, distant i tell concept property.

the core quesion this: indeed so? there save/restore solutions out there consolidate thread state, terms where the formula thread executing?

note saving an whole component state practical accessory does count, unequivocally serializing state, nonetheless only frozen accessory relocating it. an apparent solution, nonetheless bit heavyweight many time.

some questions finished pristine i pristine adequate explaining thought things. operative simulator system, unequivocally despotic manners formula controlling inside certified written. particular, finish method between vigilant construction vigilant state. interface duty pointers recreated each set adult system, biased state. state wholly consists specific allocated "attributes" any have tangible get/set duty translates between middle runtime illustration storage representation. pointers between objects, converted names. the design, an vigilant competence out storage:

object foo {
  value1: 0xff00ff00;
  value2: 0x00ffeedd;
  next_guy_in_chain: bar;
}

object bar {
  next_guy_in_chain: null;
}

linked lists never unequivocally donation chronicle structure, any vigilant represents section hardware kind.

the problem wish this, nonetheless also have threads proceed formula behavior. "behavior" here unequivocally spin state chronicle units. basically, settlement have says such changeds have finished atomic finish operations called, work, return. state stored objects. have reactive model, called "run completion", "event driven".

the proceed pondering have objects have active threads operative them, lay an almighty loop same proceed model unix threads, never terminate. box i am perplexing reasonable stored disk, nonetheless does seem presumably but interposing vm underneath.

update, october 2009: paper associated published during fdl contention 2009, checkpointing systemc.