From: XrXr@... Date: 2019-11-28T17:19:48+00:00 Subject: [ruby-core:96022] [Ruby master Bug#16380] OSX Segmentation fault at 0x0000000106e67698 / illegal hardware instruction rake install_latest Issue #16380 has been updated by alanwu (Alan Wu). I don't see anything obvious in the crash logs. As a shot in the dark, could you ask the people that have these troubles to run `gem pristine $gem_name` on all the gems they use? `gem pristine --all` works too, but might take longer. If your org uses Bundler, you can run `bundler pristine` instead. ---------------------------------------- Bug #16380: OSX Segmentation fault at 0x0000000106e67698 / illegal hardware instruction rake install_latest https://bugs.ruby-lang.org/issues/16380#change-82867 * Author: tiv (tilman voelker) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.6.5p114 (2019-10-01 revision 67812) [x86_64-darwin19] * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN ---------------------------------------- Since a while we have across our team 4 or 5 developers who run often into "Segmentation fault" on OSX machines when running a rake script. Problem: We start the rake task and sometimes it stops with a **Segmentation fault**. Environment: ruby 2.6.5p114 (2019-10-01 revision 67812) [x86_64-darwin19] But it happens also on: ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-darwin19] ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-darwin19] ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-darwin19] ruby 2.7.0preview1 (2019-05-31 trunk c55db6aa271df4a689dc8eb0039c929bf6ed43ff) [x86_64-darwin19] We have also tested some older Ruby versions without luck. It happens only on some OSX machines (especially the new MacBooks but we had it also one older machine). We use **RAKE** We use **GIT** inside of rake We use the Following GEMS: ``` ruby gem 'colorize' gem 'git' gem 'highline' gem 'os' gem 'rake' gem 'require_all' gem 'ruby-oci8' gem 'ruby-plsql' gem 'json_spec' gem 'nokogiri' gem 'rspec' gem 'rspec_junit_formatter' gem 'rubocop' gem 'rubocop-performance' ``` We are not able to reproduce the issue so far we have already tried multiple ideas in our Rake script and the investigation is going on ... ---Files-------------------------------- ruby_2019-11-28-121121_WMS111.crash (143 KB) ruby-stacktrace (68.3 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: