It would still help tremendously if somebody could implement a way to spit out all fiber backtraces…sometimes if crystal is “hung” it’s impossible to use gdb to see where it is hung at, so it feels quite blind. I have to add a bunch of STDERR.puts ’ in there to try and track its progress.
that or another idea would be a compiler mode “tracer” (like ruby tracer) that prints something to STDERR for “each and every method call” I’d love that too!
I’d be happy to contribute a couple hundred toward either of these two efforts if it would help.
See also https://github.com/crystal-lang/crystal/issues/6461