From: "matz (Yukihiro Matsumoto)" <matz@...>
Date: 2012-03-28T19:27:43+09:00
Subject: [ruby-core:43796] [ruby-trunk - Feature #6216][Feedback] SystemStackError backtraces should not be reduced to one line


Issue #6216 has been updated by matz (Yukihiro Matsumoto).

Status changed from Open to Feedback

Could you be more descriptive, please?  Comparing outputs from Ruby and JRuby, for example.

Matz.
----------------------------------------
Feature #6216: SystemStackError backtraces should not be reduced to one line
https://bugs.ruby-lang.org/issues/6216#change-25300

Author: postmodern (Hal Brodigan)
Status: Feedback
Priority: Normal
Assignee: 
Category: core
Target version: 2.0.0


When debugging "SystemStackError: stack level too deep" exceptions, it is not helpful that the backtrace is reduced to one single line. Most of the time Ruby incorrectly identifies where cycles begin, resulting in an unrelated "file:line" as the backtrace. A more useful behaviour would be to print the last 30 lines of the backtrace, and have the developer identify which "file:line" is causing the cycle. This is similar to how JRuby handles SystemStackError backtraces.


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