Benoit Daloze

We do this: https://github.com/oracle/truffleruby/blob/788cb4c1ad98bcd275277aa59f53b029423af828/lib/truffle/rbconfig.rb#L112 So core C ext files paths are made relative to the ruby home. So `--inspect.SourcePath=TRUFFLERUBY_REPO` should help.

Although `--inspect.SourcePath` is only for the Chrome Inspector protocol, I don't see the DAP equivalent option. Maybe it's supposed to be configured in the IDE somehow? cc @entlicher

A workaround until then is to remove the `cppflags

> I removed the `relative_debug_paths` line in _rbconfig.rb_ and that fixed the native extension debugging as well. That's very strange. `relative_debug_paths` is only used `if Truffle::Boot.get_option 'building-core-cexts'`, so that should...

Thanks for the report. I cannot reproduce it locally with `bundle install`. Did you pass any flags to Bundler, what was your Bundler command? It looks like it could be...

Indeed, that can be reproduced with: ``` $ gem i seven_zip_ruby Fetching seven_zip_ruby-1.3.0.gem Building native extensions. This could take a while... Successfully installed seven_zip_ruby-1.3.0 1 gem installed $ruby -w -rseven_zip_ruby...

Thank you for the report. Can you also reproduce it on CRuby or only on TruffleRuby? It sounds like it could be an issue in Oj.

Thank you for the report. truffleruby-head/truffleruby+graalvm-head is needed at least for the https://github.com/oracle/truffleruby/commit/3877eeb6d9016d796f1fbc385c908c781e870517 fix and it should also avoid that segfault you see on 22.3.0 (see https://github.com/oracle/truffleruby/issues/2801). I fixed https://github.com/rbenv/ruby-build/issues/2092....

See https://github.com/mastodon/mastodon/commit/4e4b72a1ffa18de8280a0625e322f9c55df114d1#r90590935 regarding the `GC.start` calls.

The segfault on 22.3 is very likely the same as https://github.com/oracle/truffleruby/issues/2801 so yeah fixed on `-dev`. I've run the tests with: ``` RAILS_ENV=test bundle exec rake db:migrate RAILS_ENV=test bundle exec...