Hi, I believe I mailed you guys personally on this issue last Sunday because I was not a subscriber to this list. If you didn't receive my mail, I'll have to recheck my mail settings.
Anyway, the mail was about a commit made in the ruby_1_8 branch that possibly fixes the segfault in question (it does for me at least). Can you please try the following one-line patch? http://svn.ruby-lang.org/cgi-bin/viewvc.cgi/branches/ruby_1_8/class.c?r1=22679&r2=22678&pathrev=22679 If it eliminates the segfault, I'll ask the ruby_1_8_6/ruby_1_8_7 maintainer for a merge. Thanks, On Mar 6, 7:45 am, Clive Crous <[email protected]> wrote: > In case anyone else is in my situation and is unable to migrate off > MRI 1.8.7 I've patched Sequel to work around the bug in ruby so the > spec files run in this version without a ruby seg fault. > Jeremy (quite correctly) does not want to apply this patch to Sequel > as it's a bug in ruby not Sequel causing this (as mentioned before in > this thread the bug has been fixed in ruby-core so the next ruby > release will "automatically" fix this issue). > > In the meantime if, like me, you are forced to use 1.8.7 feel free to > grab the patch in this branch of mine which will let you run the spec > files for Sequel without problems: > > http://github.com/clivecrous/sequel/tree/cater-for-segmentation-fault... > > Clive --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en -~----------~----~----~----~------~----~------~--~---
