Getting stack trace between fibers

Fabio Tudone fabtud at
Wed Oct 31 13:51:53 UTC 2018

On Wed, Oct 31, 2018 at 10:05 AM Alan Bateman <Alan.Bateman at>

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
> and the debugging APIs, but less clear (to me
> anyway) if the more user facing Fiber API will need the equivalent of
> Thread getStackTrace.

I think the same as for threads, for example monitoring and visibility in
general (e.g. in Quasar where "getStackTrace" is provided by the common
"Strand" API).

-- Fabio

More information about the loom-dev mailing list