So the current status of this is "apparent" VM bug. Is it apparent enough that for now should I stop banging my head against it from the image side?
Actually I am working 10 hour shifts the next three weeks during the power station's annual maintenance outage, so my time is probably limited anyway. cheers -ben On Mon, Apr 6, 2015 at 4:10 AM, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> wrote: > > > 2015-04-05 17:38 GMT+02:00 Ben Coman <b...@openinworld.com>: > >> >> >> On Sun, Apr 5, 2015 at 8:59 PM, stepharo <steph...@free.fr> wrote: >> >>> >>> Thanks both of you for the energy you put into Pharo. >>> The tam really appreciates. >>> This is because there are guys like you that Pharo is worth being done. >>> Thanks for the tests. >>> Esteban has apparently found the bug on the VM. >>> >>> Stef >>> >>> >> Energy breeds energy. For me it was an opportunity to learn more deep >> stuff(tm) by digging with a goal. It remains a bit beyond me, but I'm >> happy if I've been able to beat the high grass enough to flush the tiger >> into the open where the marksman can take a shot at it. >> >> Nice to flush out a VM bug (can't be too many of those left ;). Let us >> know when we can do testing on it. I guess I'll read more about it on >> [vm-dev]. >> >> cheers -ben >> > > > If it's a VM bug, the VM folks would be really really interested by a bug > report, especially if ever it may affect Eliot's branch. > Even if it's a Pharo only bug, it is still very interesting to know, > because there's allways something to learn from a bug. > So I'm all ears... > > cheers > > Nicolas >
