Issue #8591 has been updated by aaron / serendipity.cx (Aaron Stone).


This is a great find! I've been wondering what on earth the problem was. (Wish I had seen this bug months ago.)

The DL warning is just a warning, it's not a problem.

The MySQL Connector/C 6.1 should work fine in mysql2 >= 0.3.12, we fixed the version check.

Is there a way we can detect the missing gendef state and instruct the user to fix their libmysql.dll? Either at compile or load time. Should this bug be reported upstream as well, so that MySQL begins building their DLLs with the right info baked in?
----------------------------------------
Bug #8591: [BUG] Segmentation fault  ruby 2.0.0p195 (2013-05-14) [x64-mingw32]
https://bugs.ruby-lang.org/issues/8591#change-43913

Author: chmel (Josef Chmel)
Status: Third Party's Issue
Priority: Urgent
Assignee: cruby-windows
Category: platform/windows
Target version: 
ruby -v: ruby 2.0.0p195 (2013-05-14) [x64-mingw32]
Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN


rails server crashes with Segmentation fault
in pure app created with rails new . 
after installing mysql2 gem like this
gem install mysql2 -v '0.3.12b6' -- --with-opt-dir="C:\work\mysqlconnectorc61"

On Windows 7 64b with ruby 2.0 64b in C:\Ruby200-x64 installed by ruby installer rubyinstaller-2.0.0-p195-x64.exe, devkit DevKit-mingw64-64-4.7.2-20130224-1432-sfx.exe and mysql connector mysql-connector-c-6.1.0-winx64.msi.

without gem 'mysql2', '~>0.3.12b6' with gem 'sqlite3' server runs fine


-- 
http://bugs.ruby-lang.org/