Added by Falcon (Ilya Sokolov) almost 8 years ago. Updated almost 8 years ago.
c:0038 p:0015 s:0170 b:0170 l:000169 d:000169 METHOD /Users/Falcon/.rvm/gems/ruby-1.9.2-head/gems/activerecord-3.0.8/lib/active_record/connection_adapters/abstract/connection_pool.
Adding '-r openssl' would affect autloading but the location where an exception thrown is OpenSSL::SSL::SSLSocket#connect.
Does the SEGV always happens for you? It would help to show us a minimized reproducible code or concrete steps to reproduce the SEGV.
Jerome, thanks for letting us know about 'pg'. With your help I found that a similar bug and solution.
The reporter said that it was an error on OpenSSL when using a macports installation of either Postgres or Mysql. And installing from scratch or using Homebrew fixed the issue.
I checked ruby-pg gem. It links openssl by itself. For using native gems which depends on OpenSSL (such as pg and EventMachine) we need to make sure that all of OpenSSLs must be the same. Native extensions naturally uses mkmf.rb and try to detect system OpenSSL. This mismatch often occurs when you use --with-openssl-include for compiling ruby.
Ilya and Jerome, would you please make sure you're using same OpenSSL libraries for every gem you're using?
I close this as a duplicate of #4611.