<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 26, 2016 at 11:27 AM, David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com" target="_blank">lewis@mail.msen.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
That is very good news! The Cuis folks will be happy to hear about this<br>
also, as there has been recent discussion on the Cuis list about how to do<br>
a transition to Spur format.<br></blockquote><div><br></div><div>Alas the tracer is unlikely to work as one needs to add extra methods. I have been remiss in helping the Cuis folks transition. I have been distracted with 64-bit work. The situation right now is that a script that installs the revised Float (SmallFloat64 & BoxedFloat64) hierarchy needs rewriting for Cuis and I haven't got round to it. Forgive me.</div><div><br></div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
If I recall right, the issue with tracing and resuming on Cog had to do<br>
with resuming in the middle of a method of a jitted method. I don't think<br>
that I ever positively confirmed that theory, but things worked fine under<br>
an interpreter and it was a trivial step to re-save from Cog.<br></blockquote><div><br></div><div>At least from the image level the difference in e.g. pc in the active context shouldn't be visible. If it is then there's a bug in Cog.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Dave<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> I've updated the SystemTracer package to trace a Spur-format image.<br>
><br>
> This works as far as I can tell, producing a header that looks just like<br>
> the<br>
> header produced by the VM and the objects written also look good. I can<br>
> also<br>
> open the image in RSqueak, but not on Spur. It crashes immediately and<br>
> produces a Smalltalk backtrace that looks like it never manages to return<br>
> from the image-saving method (but the names in the Stack-trace all look<br>
> ok,<br>
> leading me to believe that enough objects got written ok to figure out<br>
> classes, method names, find the right Process to run and so forth).<br>
><br>
> Curiously, the old SystemTracer2 class that writes Cog-format images also<br>
> produces images that cannot be opened by Cog VMs, only Interpreter VMs. So<br>
> I<br>
> assume there are other assumptions that maybe the JIT makes when starting<br>
> up.<br>
><br>
> So my question is, what assumptions could there be, and where could I<br>
> start<br>
> looking.<br>
><br>
> Cheers,<br>
> Tim<br>
><br>
> (If you're wondering why I'm using the Smalltalk-level tracing at all - in<br>
> our quest to create (with RSqueakVM) a Squeak VM that runs Squeak code<br>
> fast<br>
> enough that we no longer have to rely on C code from plugins or optional<br>
> primitives, we're trying to see how far we can push this, and e.g. write<br>
> the<br>
> image from within itself, too.)<br>
><br>
><br>
><br>
> --<br>
> View this message in context:<br>
> <a href="http://forum.world.st/Tracing-a-Spur-Image-from-Smalltalk-tp4881224.html" rel="noreferrer" target="_blank">http://forum.world.st/Tracing-a-Spur-Image-from-Smalltalk-tp4881224.html</a><br>
> Sent from the Squeak VM mailing list archive at Nabble.com.<br>
><br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><span style="font-size:small;border-collapse:separate"><div>_,,,^..^,,,_<br></div><div>best, Eliot</div></span></div></div></div>
</div></div>