Project

General

Profile

Feature #6216

SystemStackError backtraces should not be reduced to one line

Added by postmodern (Hal Brodigan) over 8 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Target version:
[ruby-core:43794]

Description

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.


Files

stack-overflow.patch (630 Bytes) stack-overflow.patch compute full backtrace on SystemStackError drkaes (Stefan Kaes), 04/14/2013 03:36 PM

Related issues

Has duplicate Ruby master - Feature #9805: Backtrace for SystemStackErrorClosed05/05/2014Actions

Also available in: Atom PDF