Issue #21502 has been updated by jeremyevans0 (Jeremy Evans). Status changed from Open to Closed Reading https://github.com/hakivvi/frida-ruby/issues/2#issuecomment-3042173245, it looks like it was a bug in the gem that got fixed. ---------------------------------------- Bug #21502: Segfault with 3.2.8 with frida gem https://bugs.ruby-lang.org/issues/21502#change-113939 * Author: MatzFan (Brian Cohen) * Status: Closed * ruby -v: 3.2.8 * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- I've just seen a segfault executing the following code in irb with the frida gem: ``` shell $ rbenv versions * 3.2.8 (set by /home/me/.rbenv/version) $ gem install frida Fetching frida-0.1.1.gem Building native extensions. This could take a while... frida has been successfully compiled and installed, frida-core is no longer required and can be safely removed. Successfully installed frida-0.1.1 1 gem installed $ irb irb(main):001:0> require 'frida' => true irb(main):002:0> mgr = Frida::DeviceManager.new => #<CFrida::DeviceManager:0x00007fd91dbf49a8> irb(main):003:0> devices = mgr.enumerate_devices => [#<Device: id="local", name="Local System", type="local">, ... irb(main):004:0> device = devices.last => #<Device: id="emulator-5554", name="Android Emulator 5554", type="usb"> irb(main):005:0> device.is_lost => false irb(main):006:0> device.enumerate_applications (irb):6: [BUG] Segmentation fault at 0x0000000000020000 ... see attached backtrace ``` Happy to provide more information about my system setup if required. ---Files-------------------------------- segfault_3.2.8 (46.7 KB) -- https://bugs.ruby-lang.org/