From: "postmodern (Hal Brodigan)" Date: 2012-03-28T16:16:37+09:00 Subject: [ruby-core:43794] [ruby-trunk - Feature #6216][Open] SystemStackError backtraces should not be reduced to one line Issue #6216 has been reported by postmodern (Hal Brodigan). ---------------------------------------- Feature #6216: SystemStackError backtraces should not be reduced to one line https://bugs.ruby-lang.org/issues/6216 Author: postmodern (Hal Brodigan) Status: Open 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/