Benoit Daloze

Example code to repro: ```ruby def foo(a) a + 1 + 1 end loop do foo(rand(256)) end ``` Same issue on CE and EE.

One problem with this is the one I explained in https://bugs.ruby-lang.org/issues/20152#note-11: > There could be a `skip-make`/`skip-compilation` or so file which does not include `RUBY_ENGINE` in the filename and is...

Linking to https://bugs.ruby-lang.org/issues/19972 since it seems highly related. I replied there, agreed it would be best to store default & bundled gems separate from user-installed gems. > 2. Don't treat...

BTW, is there a way to disable this "install the BUNDLED WITH Bundler"? It could be a useful workaround here and in various other situations.

Another workaround is to remove the `BUNDLED WITH` section, but that needs to be done manually so rather messy. (it makes a lot of sense for Gemfile.lock files in TruffleRuby...

This happens because a custom `inspect` is modifying the object and `FrozenError` tries to inspect the receiver.

We would need a reproducer to investigate this. childprocess has IIRC 0 differences between Linux and macOS, e.g. `process.stop` is: https://github.com/enkessler/childprocess/blob/127a3d14b6db54e62961d4e8d93e65617d24f9c5/lib/childprocess/unix/process.rb#L10-L26 You could try to do the same using bare...

BTW: https://github.com/enkessler/childprocess/blob/127a3d14b6db54e62961d4e8d93e65617d24f9c5/lib/childprocess/process_spawn_process.rb#L75-L80 So ChildProcess should never use a shell around the subprocess.

Agreed, @rhenium are you OK to close this issue and the milestone? And if there any remaining TODO for OpenSSL 3.0 then I would suggest to file a new issue...

I think due to this confusion, it's basically very hard for non-CRuby devs to use benchmark-driver and understand how it works/the various modes. But this may not matter, I think...