Just in case anyone runs into the same issue, it's documented here: http://redmine.ruby-lang.org/issues/4611
For me, removing postgres solved the problem. Had planned on moving to MongoDB anyway . . . Best Wishes, Peter Begin forwarded message: > From: Peter Bell <pe...@pbell.com> > Date: May 31, 2011 9:47:58 AM EDT > To: rubyonrails-talk@googlegroups.com > Subject: Seg fault with Ruby 1.9.2 p180 and Rails 3.1 rc1 > > Hi All, > > I've got a very simple OmniAuth install. I've registered the app with > facebook and the login works fine. When Facebook runs it's callback > and tries to pull up localhost:3000/auth/facebook/callback, I get a > "page can't be displayed" in my browser and in the terminal window > where I'm running "rails server" it crashes with a Ruby SegFault. > > Here's the gist: https://gist.github.com/1000515 > > Bottom line: > Started GET "/auth/facebook" for 127.0.0.1 at 2011-05-31 09:32:48 > -0400 > /Users/peterbell/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/net/ > http.rb:678: [BUG] Segmentation fault > ruby 1.9.2p180 (2011-02-18 revision 30909) [x86_64-darwin10.7.0] > > Anyone seen anything like this before at all? I'm running 1.9.2 p180, > Rails 3.1 rc1 and the default version of OmniAuth (0.2.6) > > Any suggestions for possible work arounds? I need to knock this app > out pretty quickly, and I love OmniAuth, but this is a bit of a > surprise. > > Can't drop down to Ruby 1.8.7 or Rails 3.0.7/8. Open to trying > OmniAuth 1.0-beta if you think it'd help. > > Anyone seen anything like this before? Any input appreciated. > > Thanks, > Peter -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
