[Vm-dev] VM Maker: VMMaker.oscog-nice.1733.mcz

Esteban Lorenzano estebanlm at gmail.com
Fri Mar 18 16:28:40 UTC 2016


btw… that means it works ok in your VMs? 
I would be very surprised, since error seems to happen in places I never seen before (which usually means we didn’t change anything there).

Esteban

> On 18 Mar 2016, at 16:56, Eliot Miranda <eliot.miranda at gmail.com> wrote:
> 
> Hi Esteban,
> 
> 
> On Mar 18, 2016, at 8:23 AM, Esteban Lorenzano <estebanlm at gmail.com <mailto:estebanlm at gmail.com>> wrote:
> 
>> 
>>> On 18 Mar 2016, at 16:11, Nicolas Cellier <nicolas.cellier.aka.nice at gmail.com <mailto:nicolas.cellier.aka.nice at gmail.com>> wrote:
>>> 
>>> 
>>> 
>>> 2016-03-18 16:00 GMT+01:00 Esteban Lorenzano <estebanlm at gmail.com <mailto:estebanlm at gmail.com>>:
>>> 
>>> Hi Nico,
>>> 
>>> somewhere between this and VMMaker.oscog-dtl.1730 all PharoVMs become unusable :(
>>> are you aware of this?
>>> maybe I’m forgetting something in my builds?
>>> 
>>> cheers,
>>> Esteban
>>> 
>>> 
>>> Hi Esteban,
>>> Please provide more feedback
>>> - can/can't compile ?
>>> - VM crash ? instantly or on specific operations ?
>> can compile, but image is unusable (no refresh of UI… error with Bitmaps I think). 
>> 
>>> - all OS or OS specific ?
>> all environments (mac, linux and win) have this problem.
>> 
>>> - which flavour - stack/cogit x spur/v3 x 32/64 bits ?
>>>   I presume cogit-spur-32bits for Pharo head?
>> yes
>> 
>>> Maybe a few explanations accompanying a Jenkins link would do it
>> 
>> I don’t know what more to say :)
>> but if you download: 
>> 
>> wget -O- get.pharo.org/50+vmLatest <http://get.pharo.org/50+vmLatest> | bash 
>> 
>> and execute it… you will see the problem.
>> 
>> and that does not happens if you execute 
>> 
>> wget -O- get.pharo.org/50+vm <http://get.pharo.org/50+vm> | bash 
>> 
>> (the only difference between those VMs are your commits).
> 
> Some things to try (Clément is across the hall; he can help)
> 
> 1. build an assert-enabled VM and run this.  You may get very useful error information.  You can use the -trace flag to get it to output the sends the VM makes and see where the first error is
> 
> 2. Open the image in the simulator, but that may be difficult with pharo cuz it uses so many external libraries.  Nite that you can still, with a little effort, do this but you have to write the plugin simulation code that maps from calls in the simulator to calls against the host VM's facilities.  For example, in the simulator the FilePluginSimulator defers to the host Smalltalk system to access files so the simulated VM can still access files just like the real VM, which defers to the stdio library or win32 APIs to access files.
> 
> The simulator is not just worth maintaining it is /essential/ to being able to debug the VM effectively.  It should be a goal to have the Pharo image runnable in the simulator.
> 
>> 
>> cheers, 
>> Esteban
>> 
>>> 
>>> I've experimented macosx stack spur 64 bits with simulator,
>>> and I use most of these changes in my own VM branch, except the fetch64/store64 message sends
>>> I'll check ASAP (this will be tonight)
>>> 
>>> Nicolas
>>> 
>>>  
>>> > On 17 Mar 2016, at 22:49, commits at source.squeak.org <mailto:commits at source.squeak.org> wrote:
>>> >
>>> >
>>> > Nicolas Cellier uploaded a new version of VMMaker to project VM Maker:
>>> > http://source.squeak.org/VMMaker/VMMaker.oscog-nice.1733.mcz <http://source.squeak.org/VMMaker/VMMaker.oscog-nice.1733.mcz>
>>> >
>>> > ==================== Summary ====================
>>> >
>>> > Name: VMMaker.oscog-nice.1733
>>> > Author: nice
>>> > Time: 17 March 2016, 11:45:52.436 pm
>>> > UUID: cc4513ea-67e5-4b41-b7bd-2fc790ac0102
>>> > Ancestors: VMMaker.oscog-nice.1732
>>> >
>>> > Oups (Oops) forgot the <doNotGenerate> for simulated #stSizeOf: version.
>>> >
>>> > =============== Diff against VMMaker.oscog-nice.1732 ===============
>>> >
>>> > Item was changed:
>>> >  ----- Method: SpurMemoryManager>>stSizeOf: (in category 'object access') -----
>>> >  stSizeOf: oop
>>> >       "Return the number of indexable fields in the receiver"
>>> > +     <doNotGenerate>
>>> >       ^oop basicSize!
>>> >

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20160318/1887c7be/attachment-0001.htm


More information about the Vm-dev mailing list