When using a debugger with coroutines in IntelliJ, I am confused about the little information the call stack provides. As coroutines are a language level feature and each coroutine should have complete knowledge over its own call stack, I would expect to be able to see the entire stack basically starting from the program entry point over multiple suspend-calls down to the breakpoint.
However, it seems that as soon as there is a switch in coroutine execution (e.g. because of a call to delay), the stack trace just goes into the internal functions of the scheduler and is lost there.
Is this something I just don’t know how to do or is it actually not possible in IntelliJ right now? In case of the latter, is this somehow intended or technically impossible or is it a feature that Jetbrains just didn’t get to implement yet?
submitted by /u/Wurstinator
[link] [comments]
