Not working with ruby 2 about binding_of_caller

[envygeeks]

You are on Ruby 2.0 RC1 from the looks of it. Please update to stable Ruby 2.0 with: rvm upgrade 2.0.0-rc1 2.0.0

[envygeeks]

@mpapis Maybe in RVM 1.20 we can start warning about using RC's when we know there are stable Rubies?

[mpapis]

rvm will always use the latest version - unless users hardcode 2.0.0-rc1 / or any other patch level like 1.9.3-p392

[envygeeks]

He already had it installed, the point is we should possibly (I'm iffy on this) warn them if they still have an old RC installed and we know there is a newer stable for that RC available. Case in point is I install RC1 a couple of months ago, come back and here come the errors, it would be good if we warned them that their Ruby is an RC version and there is a new stable version (just for RC's not for 1.8.7 or anything like that.)

[mpapis]

yeah we could ad a warning ... simplest way in a hook, you can open a ticket for that

[manoj2411]

Thanks, i will update and try again

[j15e]

+1 on ruby 2.0.0-p0

Server crash (too long) :

http://j15e.s3.amazonaws.com/dump/ruby_2013-05-03-padrino.crash

OSX crash reports :

http://j15e.s3.amazonaws.com/dump/ruby_2013-05-02-155242_jpdoyle-mbp.crash
http://j15e.s3.amazonaws.com/dump/ruby_2013-05-03-095923_jpdoyle-mbp.crash

[badosu]

Is there a way to reproduce this error?

[j15e]

I haven't found a precise way to reproduce and now with 2.0.0-p195 I am not having this issue anymore. I would say "but-that-is-no-more-a-bug".

[badosu]

These problems which are magically fixed by patches on MRI can be fixed here?