From: "jeremyevans0 (Jeremy Evans) via ruby-core" Date: 2025-10-03T16:53:55+00:00 Subject: [ruby-core:123388] [Ruby Bug#21624] [BUG] Segmentation fault at 0x0000000000000000 Issue #21624 has been updated by 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 mentioned, using mysql 0.5.6 should work around the issue until mysql2 releases a fixed gem. ---------------------------------------- Bug #21624: [BUG] Segmentation fault at 0x0000000000000000 https://bugs.ruby-lang.org/issues/21624#change-114759 * Author: mriffe (Mel Riffe) * Status: Third Party's Issue * ruby -v: ruby 3.3.9 (2025-07-24 revision f5c772fc7c) [x86_64-linux] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- 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. ---Files-------------------------------- error.out (381 KB) -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/