Getting stack trace between fibers
Alan Bateman
Alan.Bateman at oracle.com
Wed Oct 31 08:05:29 UTC 2018
On 30/10/2018 19:58, Ron Pressler wrote:
> Hi.
>
> Obtaining stack traces will not be done through the shadow thread mechanism, but through a different one, which is not yet implemented.
> The shadow thread is not a real thread (i.e. it is only a Java Thread object, but one that is not backed by a kernel thread).
> Perhaps there will be a getStackTrace method on Fiber, in which case that is the one that will need to be used in this (excellent) test.
>
One thing that would be useful is to get some examples on where it's
important to walk another fiber's stack. No issue with a fiber walking
its own stack of course, we have StackWalker for that. I suspect we'll
have to do several updates in the serviceability area, maybe to the
java.lang.management and the debugging APIs, but less clear (to me
anyway) if the more user facing Fiber API will need the equivalent of
Thread getStackTrace.
-Alan
More information about the loom-dev
mailing list