Bug #21624: [BUG] Segmentation fault at 0x0000000000000000

• Status: Third Party's Issue
• Assignee: -
• Target version: -
• ruby -v: ruby 3.3.9 (2025-07-24 revision f5c772fc7c) [x86_64-linux]
• Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN

[mriffe (Mel Riffe)]

The attached file contains the core dump I receive running bin/rake db:setup in a Ruby on Rails project. I'm looking for help on where the actual problem lies. Any assistance will be appreciated.

Background
I'm moving from a Mac Book Pro to an Ubuntu (24.04) Desktop, as my daily development machine.

At first I suspected the mysql2 gem, so I uninstalled it, and installed it again. I verified I have libmysqlclient-dev installed; I figure the gem wouldn't compile without the headers but I wanted to be sure.

I do not have experience debugging core dumps/segmentation faults. Instruction would be greatly appreciated.

What additional information can I provide to aid running down and solving this issue? Plus, if this is not the location for this notification, kindly point me in the right direction.

Thank you for your time and energy.

[luke-gru (Luke Gruber)]

Thanks for the report. Have you tried locking the mysql2 gem to version 0.5.6? Version 0.5.7 was just released a couple of weeks ago.

[jeremyevans0 (Jeremy Evans)]

• Status changed from Open to Third Party's Issue

Probably hitting this issue: https://github.com/brianmario/mysql2/pull/1410 . As @luke-gru (Luke Gruber) mentioned, using mysql 0.5.6 should work around the issue until mysql2 releases a fixed gem.

[mriffe (Mel Riffe)]

jeremyevans0 (Jeremy Evans) wrote in #note-2:

Probably hitting this issue: https://github.com/brianmario/mysql2/pull/1410 . As @luke-gru (Luke Gruber) mentioned, using mysql 0.5.6 should work around the issue until mysql2 releases a fixed gem.

luke-gru (Luke Gruber) wrote in #note-1:

Thanks for the report. Have you tried locking the mysql2 gem to version 0.5.6? Version 0.5.7 was just released a couple of weeks ago.

Using 0.5.6 works - thank you for the suggestion.

I guess I shouldn't be surprised I can use 0.5.7 in mac-land, but not linux-land.

I consider this issue addressed. And will be holding off updating the mysql2 gem for the time being.

Thank you for your patience and understanding.