Benoit Daloze

I'm not sure if any tool differentiates between `:c_call` and `:call` events, I would guess not. So we could just do nothing on `:c_call` but trigger `:call` on any method...

The TracePoint `:call` event is also used by byebug: ``` $ ruby -Iext -Ilib exe/byebug ~/test.rb core/tracepoint.rb:24:in `block in initialize': unknown event: call (ArgumentError) from core/tracepoint.rb:19:in `each' from core/tracepoint.rb:19:in `initialize'...

Is there maybe a way to "disable plugins" for `pry` as a workaround? We seem to have some logic for calls for `set_trace_func` but not for `TracePoint`. We should add...

As a note, TruffleRuby already supports a couple debuggers: * VSCode: https://www.graalvm.org/tools/vscode/graalvm-extension/#ruby-debugging * Chrome: https://www.graalvm.org/tools/chrome-debugger/

Yes, byebug doesn't work currently on TruffleRuby, and that error is due to the call/c_call TracePoint not being implemented yet. There are already GUI debuggers for TruffleRuby however: https://github.com/oracle/truffleruby/issues/1672#issuecomment-882436749

I don't see any `--vm.Xmx2g` in this log, where is it set? https://gitlab.com/honeyryderchuck/rodauth-oauth/-/jobs/1883707290 Both failing runs seems to be on truffleruby 21.3.0 and the passing one on truffleruby 21.2.0 (based...

Something that might make a difference is that @headius was running GraalVM on JDK 11 and not JDK 8. Currently we still recommend JDK8 for TruffleRuby because we test it...

@headius Could you try with GraalVM JDK 8 instead of 11 and see if it still happens?

I think the solution here is to just pass an Encoding to `Integer#chr`: ```ruby 226.chr(Encoding::UTF_8) ``` Then it should work fine to export it. @fniephaus Could you try that? For...

Yes, that works in GraalVM: ``` ruby> Polyglot.export('string', 226.chr(Encoding::UTF_8)) "â" ``` @fniephaus Is that OK for your use case?