Hi Kouji,
Some of the macruby specs are known to crash in certain environments. I haven't
had the chance to look at this yet. You might want to try `rake spec:rubyspec'
instead, in the meantime.
Laurent
On Dec 16, 2010, at 10:18 PM, Takao Kouji wrote:
> Hi, the 'rake spec:ci' is aborting usin
Hi Yasu,
I believe I identified what specific commit broke your app, and I committed a
potential fix in r5043.
Could you try trunk or the next nightly build and let me know if it's still
broken for you?
Thanks,
Laurent
On Dec 14, 2010, at 6:30 PM, Yasu Imao wrote:
> I filed a ticket and atta
Hi, the 'rake spec:ci' is aborting using r5042.
- begin output -
cymric$ rake spec:ci
(in /Users/kouji/work/MacRuby/MacRuby)
rm -rf rubyspec_temp
./mspec/bin/mspec ci -B ./spec/macruby.mspec :full
MacRuby 0.9 (ruby 1.9.2) [universal-darwin10.0, x86_64]
.*** Dispatch block exited p
On Dec 16, 2010, at 1:36 AM, Eloy Duran wrote:
> It unfortunately still causes a segfault for my FSEvents RubyCocoa code in
> Kicker :(
>
> $ sudo gem install kicker
> $ kicker -e 'ls -l'
>
> Then after a change to a file in the current directory:
>
> Program received signal EXC_BAD_ACCESS, Co
I believe that it's normal that peepopen crashes since it was precompiled
with the old BS so you would need to recompile form source.
- Matt
On Thu, Dec 16, 2010 at 10:36 AM, Eloy Duran wrote:
> It unfortunately still causes a segfault for my FSEvents RubyCocoa code in
> Kicker :(
>
> $ sudo gem
It unfortunately still causes a segfault for my FSEvents RubyCocoa code in
Kicker :(
$ sudo gem install kicker
$ kicker -e 'ls -l'
Then after a change to a file in the current directory:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: 13 at address: 0x
0
