Vm-dev July 2011

vm-dev@lists.squeakfoundation.org

31 participants
164 discussions

VM Maker: VMMaker-oscog-IgorStasenko.92.mcz
by squeak-dev-noreply＠lists.squeakfoundation.org 01 Jul '11

01 Jul '11

Igor Stasenko uploaded a new version of VMMaker to project VM Maker: http://www.squeaksource.com/VMMaker/VMMaker-oscog-IgorStasenko.92.mcz ==================== Summary ==================== Name: VMMaker-oscog-IgorStasenko.92 Author: IgorStasenko Time: 30 June 2011, 11:28:44 pm UUID: 9823f129-7da4-4aee-967f-2bce7feb6770 Ancestors: VMMaker-oscog-IgorStasenko.91, VMMaker.oscog-eem.90 - merge with VMMaker.oscog-eem.90 (now Cog VMs should work stable again)

1 0

Re: Cog JIT crashing
by Igor Stasenko 01 Jul '11

01 Jul '11

resending, because original attached .png was too big On 30 June 2011 19:31, Igor Stasenko <siguctua(a)gmail.com> wrote: > Hello, > > with latest updates, a Cog VMs simply crashing quickly after image startup. > > I strongly suspect that the bug in jit, because stack VMs built using > same VMMaker sources are working well. > You can check the: > https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Cog%20Mac%20Carbon/ > vs > https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/StackVM%20Mac%20Carbon/ > > > of course, first thing which i suspected is that my merge was bad, so > i also tried to build VM using VMMaker.oscog-eem.88 > but it also crashing with same symptoms and always in same place (in > ceSendsupertonumArgs() , with rcvr argument containing non-oop (-36 , > sometimes 0, sometime -24) ) > > See the screenshot in attachment. > > I also checked win32 Cog build.. same result: immediate crash after > selecting an image to open. > > -- > Best regards, > Igor Stasenko AKA sig. > -- Best regards, Igor Stasenko AKA sig.

2 3

VM Maker: VMMaker.oscog-eem.90.mcz
by squeak-dev-noreply＠lists.squeakfoundation.org 01 Jul '11

01 Jul '11

Eliot Miranda uploaded a new version of VMMaker to project VM Maker: http://www.squeaksource.com/VMMaker/VMMaker.oscog-eem.90.mcz ==================== Summary ==================== Name: VMMaker.oscog-eem.90 Author: eem Time: 30 June 2011, 4:18:59 am UUID: efb3c8a3-db33-4387-b560-49b3d9f04cde Ancestors: VMMaker.oscog-eem.89 Slang: Fix translation of statement lists in context of ? : . Cogit: Fix remove inst var typos die to inst var renames. Fix assert. Cog Interpreters: Informative printing for Aliens.

1 0

Tracking Hudson builds
by Igor Stasenko 01 Jul '11

01 Jul '11

I am thinking, how is better to track Hudson builds. Currently VM reports a build by taking a VMMaker package version. But it is incomplete information: - there is no evidence which sources been used and which configuration of CMakeVMMaker been used. Hudson fetching everything from git, so using git hash number is a complete pointer to the sources. But in addition, i need to specify which configuration been used (since there are many of them). Actually i think that the more information we put, the easier it would be to track down, which VM are used. So, my question, what is your preferences? Because currently 'Cog 4.0.0' as well as 'VMMaker-foo-bar.xyz' says almost nothing :) -- Best regards, Igor Stasenko AKA sig.

2 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Vm-dev July 2011