Re: [Vm-dev] SystemTracer64 progress

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [Vm-dev] SystemTracer64 progress

jannik laval
Hi David,

I cannot write my changes.
So you can have them in attachment.

In these .cs, there is a merge with your version .15.
And it works with Pharo.

Cheers

Jannik





On Jan 12, 2010, at 04:55 , David T. Lewis wrote:

>
> Over the weekend I made some progress in getting SystemTracer updated
> to do 64-bit image tracing. Previously SystemTracer64 did not work on
> little-endian machines (Mantis 5240). This is corrected now, and the
> code is on SqueakSource in project "SystemTracing".
>
> I can now trace a Squeak 3.10.2 image to 64-bit format on my Linux
> AMD box (little endian), producing a runnable 64-bit image. For
> an up to date Squeak trunk image, I can trace a 64 image that
> loads and runs (display opens and things start working), but that
> has problems with resuming its background processes (low space
> watcher etc). Possibly it's related to the block closure changes,
> although I believe there was an earlier report of a Pharo image
> with block closures being successfully traced to 64 bit format.
>
> Dave
>



_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1-System-Tracing-forPharo.cs (61K) Download Attachment
2-SystemTracing-dtl.15.1.cs (110K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Vm-dev] SystemTracer64 progress

David T. Lewis
On Tue, Jan 12, 2010 at 08:31:11AM +0100, Laval Jannik wrote:

>
> On Jan 12, 2010, at 04:55 , David T. Lewis wrote:
>
> > Over the weekend I made some progress in getting SystemTracer updated
> > to do 64-bit image tracing. Previously SystemTracer64 did not work on
> > little-endian machines (Mantis 5240). This is corrected now, and the
> > code is on SqueakSource in project "SystemTracing".
> >
> > I can now trace a Squeak 3.10.2 image to 64-bit format on my Linux
> > AMD box (little endian), producing a runnable 64-bit image. For
> > an up to date Squeak trunk image, I can trace a 64 image that
> > loads and runs (display opens and things start working), but that
> > has problems with resuming its background processes (low space
> > watcher etc). Possibly it's related to the block closure changes,
> > although I believe there was an earlier report of a Pharo image
> > with block closures being successfully traced to 64 bit format.
> >
>  
> Hi David,
>
> I cannot write my changes.
> So you can have them in attachment.
>
> In these .cs, there is a merge with your version .15.
> And it works with Pharo.

Jannik,

Thank you for sending this. I will compare and merge as soon as I
have some more free time.

Also, your PharoCore64-1.1-11152-UNSTABLE image works fine on my
Linux box.

Dave


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [Vm-dev] SystemTracer64 progress

jannik laval
Hi Dave,

Thank you for your feedback :),
Now, in the PharoCore64, some tests crash or loops.

I will see that :)

Cheers,
Jannik

On Jan 12, 2010, at 13:29 , David T. Lewis wrote:

>
> On Tue, Jan 12, 2010 at 08:31:11AM +0100, Laval Jannik wrote:
>>
>> On Jan 12, 2010, at 04:55 , David T. Lewis wrote:
>>
>>> Over the weekend I made some progress in getting SystemTracer updated
>>> to do 64-bit image tracing. Previously SystemTracer64 did not work on
>>> little-endian machines (Mantis 5240). This is corrected now, and the
>>> code is on SqueakSource in project "SystemTracing".
>>>
>>> I can now trace a Squeak 3.10.2 image to 64-bit format on my Linux
>>> AMD box (little endian), producing a runnable 64-bit image. For
>>> an up to date Squeak trunk image, I can trace a 64 image that
>>> loads and runs (display opens and things start working), but that
>>> has problems with resuming its background processes (low space
>>> watcher etc). Possibly it's related to the block closure changes,
>>> although I believe there was an earlier report of a Pharo image
>>> with block closures being successfully traced to 64 bit format.
>>>
>>
>> Hi David,
>>
>> I cannot write my changes.
>> So you can have them in attachment.
>>
>> In these .cs, there is a merge with your version .15.
>> And it works with Pharo.
>
> Jannik,
>
> Thank you for sending this. I will compare and merge as soon as I
> have some more free time.
>
> Also, your PharoCore64-1.1-11152-UNSTABLE image works fine on my
> Linux box.
>
> Dave
>




_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project