[Ironruby-core] Preparing 1.1.2 release

Tomas Matousek Tomas.Matousek at microsoft.com
Mon Feb 7 18:20:30 EST 2011

Great! I spent some time to make xbuild happy :), I'm glad it works on non-Windows boxes as well.

I filed a couple of Mono bugs (crashes) yesterday:

http://bugzilla.novell.com/show_bug.cgi?id=669808<https://bugzilla.novell.com/show_bug.cgi?id=669808> (GetCustomAttributes crash)
http://bugzilla.novell.com/show_bug.cgi?id=669815 (non-deterministic crash in /nointerpret)

So this might be hitting one of them. Or another. I guess we can either wait until these are fixed and try again or try to narrow the Rubygems crash down to a simpler repro.


From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Thibaut Barrère
Sent: Monday, February 07, 2011 2:54 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Preparing 1.1.2 release

I'm cloning it right now (then I'll look where is Ruby.sln, because I have no idea yet :-)). I'll report back here after doing a few basic tests.

I can report the compile went without any issue as long as I'm on Mono 2.10 RC2.

I was able to start "mono ir.exe" and do a couple of things. require "rubygems" raised a SIGSEGV:

/tmp/mono-gdb-commands.2Rimy1:1: Error in sourced command file:
unable to debug self

Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.

Abort trap

But well - it already compiles out of the box, which is good!

-- Thibaut
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20110207/18124c5b/attachment.html>

More information about the Ironruby-core mailing list