Issue #16815 has been updated by Eregon (Benoit Daloze).


I think this makes sense and can definitely be useful for debugging.

If called on a Fiber of another Thread, that might be slow on non-GIL implementations, but that's the same as Thread#backtrace so I think not really an issue.

----------------------------------------
Feature #16815: Implement Fiber#backtrace
https://bugs.ruby-lang.org/issues/16815#change-85279

* Author: ioquatix (Samuel Williams)
* Status: Open
* Priority: Normal
----------------------------------------
Previously discussed here: https://bugs.ruby-lang.org/issues/8215

Add a new method `Fiber#backtrace`. It would produce a backtrace similar to how `Thread#backtrace` works.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>