Benoit Daloze

Ah I forgot to backlink here but I filed https://bugs.ruby-lang.org/issues/21640

It looks like it's trying to read some `double` out of a null pointer, from hs_err: ``` siginfo: si_signo: 11 (SIGSEGV), si_code: 128 (SI_KERNEL), si_addr: 0x0000000000000000 ``` If you have...

We use posix_spawnp() which might not always tell us that difference. Similar issue when Process.spawn uses the shell, and this also happens on CRuby. But for the `chdir` case reported...

`flock(2)` is not that portable and e.g. old Solaris had significant bugs with it. I wouldn't expect RubyGems to rely on such a low-level under-specified API. What about using `open(O_CREAT|O_EXCL)`...

It seems possible that the StackOverflowError causes the segfault. In your log here it seems to cause: ``` # Internal Error (upcallLinker.cpp:137), pid=47338, tid=2307 # fatal error: Unrecoverable uncaught exception...

Do you have an example CocoaPods command (and necessary files if any) that you would like to run so we can test if having that jar on Maven is enough...

FWIW I tried to install cocoapods with TruffleRuby jars on classpath and: ``` $ $ mx ruby_from_classpath --skip-build -S gem i cocoapods Fetching nanaimo-0.4.0.gem Fetching colored2-3.1.2.gem Fetching claide-1.1.0.gem Fetching CFPropertyList-3.0.7.gem...

Installing via a TruffleRuby standalone works, e.g. via `cd $HOME/tmp/cocoapods-gem-home && GEM_HOME=$PWD gem i cocoapods`. And then using it works: ``` $ GEM_HOME=$HOME/tmp/cocoapods-gem-home mx ruby_from_classpath --skip-build -S pod --version 1.16.2...

> What "magic" does the `bin/ruby` launcher script do on top of running `org.truffleruby.launcher.RubyLauncher` to make the installation of Gems work? Some `LD_LIBRARY` stuff I guess? No `LD_LIBRARY` and no...

Giving a little bit more thoughts on this, I think using `RubyLauncher` won't work for such a use case, because it always does `System.exit(exitCode)`, which is natural for a launcher...