From: "sam.saffron (Sam Saffron)" <sam.saffron@...>
Date: 2012-12-10T10:20:22+09:00
Subject: [ruby-core:50723] [ruby-trunk - Feature #7436] Allow for a "granularity" flag for backtrace_locations


Issue #7436 has been updated by sam.saffron (Sam Saffron).


@matz keep in mind, people are already hacking and using this feature externally 

https://github.com/banister/binding_of_caller

and 

https://github.com/charliesome/better_errors
----------------------------------------
Feature #7436: Allow for a "granularity" flag for backtrace_locations
https://bugs.ruby-lang.org/issues/7436#change-34572

Author: sam.saffron (Sam Saffron)
Status: Assigned
Priority: Normal
Assignee: matz (Yukihiro Matsumoto)
Category: core
Target version: next minor


related to http://bugs.ruby-lang.org/issues/7051

Sometimes one need less information (or more information) associated with backtraces.

It would be nice if one could send in a separate flag informing the VM about the granularity of information required, eg: 

caller_locations(0,-current_depth, BacktraceInfo::Label & BacktraceInfo::Lineno)

This allows for one to take quicker backtraces if they need less information, additionally BacktraceInfo::Bindings and BacktraceInfo::Klass could be added which allow you to gather more information for heavy profiling / diagnostics. 
 




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