Actions
Backport #10243
closedUpdated by usa (Usaku NAKAMURA) over 9 years ago
Unfortunately, the necessary information is lacking this log. (It is not your fault.)
This is not a problem of ruby itself, in my intuition.
Can you always reproduce this problem?
And, can you make a small code to reproduce this?
Updated by usa (Usaku NAKAMURA) over 9 years ago
- Status changed from Open to Feedback
I forgot to say an important thing.
We have already ended the normal bug fix phase of the mentenance of ruby 1.9.3.
This means that if we find the cause of the SEGV, we will not release the fix for 1.9.3.
You should try to update ruby to 2.1 or 2.0.0.
Updated by jeremyevans0 (Jeremy Evans) almost 5 years ago
- Status changed from Feedback to Closed
Actions
Like0
Like0Like0Like0