I do not understand. I sent the mail with a reproducible case twice (one is just below) :)

Is this enough? Could you reproduce it?

Doru


On Tue, Mar 12, 2013 at 9:36 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Hi Doru,

We are working hard to try to fix the vm stability issues and users help is the only way we can have enough crash cases to debug.�
Sending a mail to the list with a reproducible case is the best way to help up fix the vm.

Any report is welcomed :)

Esteban�

On Mar 12, 2013, at 9:20 AM, Tudor Girba <tudor@tudorgirba.com> wrote:

Great.

Is there anything I can do to help fixing the problem? (my problem is that I do not even know where to start)

As you can imagine this is an important blocker for the Moose team.

Cheers,
Doru




On Mon, Mar 11, 2013 at 9:58 PM, stephane ducasse <stephane.ducasse@free.fr> wrote:
thanks doru!


> Hi,
>
> Where should I report Pharo VM crashes with Pharo 2.0?

here first :)

>
> In particular, I wanted to report the problem related to running Moose tests from the command line:
>
> ---
> You can reproduce it on Mac, quite consistently: just run the attached script (you need to have wget installed), or do it manually:
>
> 1. download and unzip the latest Moose 4.8:
> https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastSuccessfulBuild/artifact/Moose-latest-dev-4.8.zip
> 2. download and unzip the latest Pharo VM:
> http://pharo.gforge.inria.fr/ci/vm/pharo/mac/pharo-mac-latest.zip
> 3. execute:
> ./Pharo.app/Contents/MacOS/Pharo ./Moose-latest-dev-4.8.image moosetest
>
> The VM crashes, but there is no trace of the error.
> ---
>
>
> Cheers,
> Doru
>
>
> --
> www.tudorgirba.com
>
> "It's not what we do that matters most, it's how we do it."
>
> <crasher.sh>





--

"Every thing has its own flow"




--
www.tudorgirba.com

"Every thing has its own flow"