Expose ec -> backtrace (internal) and use it to implement fiber backtrace.

See <https://bugs.ruby-lang.org/issues/16815> for more details.

1 files changed, 10 insertions, 0 deletions

diff --git a/vm_backtrace.c b/vm_backtrace.c
index 04b696c638..ba99527958 100644
--- a/vm_backtrace.c
+++ b/vm_backtrace.c
@@ -996,6 +996,16 @@ rb_vm_thread_backtrace_locations(int argc, const VALUE *argv, VALUE thval)
     return thread_backtrace_to_ary(argc, argv, thval, 0);
 }
 
+VALUE rb_vm_backtrace(int argc, const VALUE * argv, struct rb_execution_context_struct * ec)
+{
+    return ec_backtrace_to_ary(ec, argc, argv, 0, 0, 1);
+}
+
+VALUE rb_vm_backtrace_locations(int argc, const VALUE * argv, struct rb_execution_context_struct * ec)
+{
+    return ec_backtrace_to_ary(ec, argc, argv, 0, 0, 0);
+}
+
 /*
  *  call-seq:
  *     caller(start=1, length=nil)  -> array or nil