Issue #8263 has been updated by ko1 (Koichi Sasada).

Assignee set to ko1 (Koichi Sasada)

Sorry, I can't understand what is your proposal.

At first example <https://gist.github.com/halorgium/f63abf177a96d7113ce3>,
there is only "thread.backtrace". However, we have already Thread#backtrace.

p Thread.current.backtrace
#=>
ruby 2.1.0dev (2013-03-18 trunk 39808) [i386-mswin32_100]
["t.rb:2:in `backtrace'", "t.rb:2:in `<main>'"]

----

BTW, please add more specific description.

For example, Rdoc style description for proposed methods
is very welcome because we can understand your proposal
and we (especially I, who is not good English writer)
can copy this document to implemented source code!


----------------------------------------
Feature #8263: Support discovering yield state of individual Fibers
https://bugs.ruby-lang.org/issues/8263#change-38971

Author: halorgium (Tim Carey-Smith)
Status: Open
Priority: Normal
Assignee: ko1 (Koichi Sasada)
Category: 
Target version: 


=begin
Related to #8215, when debugging a multi-Fiber application or library it is useful to be able to look at the stack for the (({Thread})) which is possible right now. 
Currently it is not possible to discover where the Fiber was yielded. 

Is this something that could be added?

((<Thread.backtrace example|URL:https://gist.github.com/halorgium/f63abf177a96d7113ce3>))
=end


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