From: "charliesome (Charlie Somerville)" Date: 2012-12-10T11:29:41+09:00 Subject: [ruby-core:50725] [ruby-trunk - Feature #7436] Allow for a "granularity" flag for backtrace_locations Issue #7436 has been updated by charliesome (Charlie Somerville). =begin Why not introduce a (({$DEBUG})) variable that tells the runtime to enable introspective features like this at the cost of performance? I would love for better_errors to run on JRuby, but at the moment it can't since JRuby leans too far towards the performance side of the argument and there's no way to tell it to disregard performance in favour of debuggability. =end ---------------------------------------- Feature #7436: Allow for a "granularity" flag for backtrace_locations https://bugs.ruby-lang.org/issues/7436#change-34575 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/