On 09/21/2011 11:22 PM, Paolo Bonzini wrote:
> On Wed, Sep 21, 2011 at 19:24, Holger Hans Peter Freyther
> <[email protected]> wrote:
>> Hi,
>>
>> thanks to yours and Gwenael's work I move from screen/gst to image and
>> gst-remote. Today I have found a funny bug and look for some hints.
>
> So you want the value of the millisecond clock to be restored when you
> resume a snapshot? Makes sense.
but there must be more to this. E.g. even if I save the image near millisecond
clock of 0... the task does not run..
$ cat cat foo.st
Eval [
Time millisecondClockValue printNl.
Smalltalk at: #FOO put: [
[(Delay forSeconds: 3) wait. Time millisecondClockValue printNl]
repeat] fork.
ObjectMemory snapshot: 'foo.img'.
stdin next
]
$ gst -i foo.st
"Global garbage collection... done"
0
"Global garbage collection... done"
3001
6001
^CObject: FileStream new "<-0x4c82c6a0>" error: interrupted!!!
...
UndefinedObject>>executeStatements (foo.st:7)
$ gst -I foo.img
GNU Smalltalk ready
st> stdin next
nothing even if the millisecond clock should pass nicely,
i will spend the next half an hour on it and maybe I find something...
_______________________________________________
help-smalltalk mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-smalltalk
