New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segfaults with ruby2.0 #32
Comments
According to Travis, all versions of Ruby look ok. I'm wondering if this was just a bad Ruby build or something? |
Hi, I was optimistic because I couldn't reproduce this bug immediately, but after running the testsuite about 10 times on Debian sid, with ruby 2.0.0p384, I got the following backtrace:
|
I am attempting to reproduce this locally on OS X, and if that fails I'll try to test on a system more similar to yours. No leads, no theories. |
It also occurs to me this could be a Ruby 2.0 bug. Could you try to report it to ruby core and see if maybe they have a theory as to what is happening? |
Ok, I realized that thread_safe doesn't even include an extension for MRI, so this is almost certainly an MRI issue. Closing in favor of https://bugs.ruby-lang.org/issues/9649 (please comment and follow that issue). |
@headius sorry, should have looked into this. You are right - on MRI |
Hi,
it was found by automatic rebuilding of Debian archive that ruby thread_safe library segfaults with ruby2.0:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735861
Could you please take a look at that?
I can easily reproduce the bug with ruby2.0:
Ondrej
The text was updated successfully, but these errors were encountered: