As far as I understand, this has been fixed. The stack trace is
fully printed except in the case of a stack overflow.
At RubyKaigi'08 in Tsukuba, Akira Tanaka used this as one of the
examples of how to convince Matz to make some changes.

Regards,    Martin.

At 13:04 08/11/24, Jim Weirich wrote:
>
>On Nov 23, 2008, at 9:49 PM, Yehuda Katz wrote:
>
>> In case this is not already resolved, I'd like to request the  
>> removal of ...
>> 19 levels ... in non-rescued Ruby stack traces. Or, at the very  
>> least, the
>> ability to turn of the truncation via an option. With more and more  
>> Ruby
>> code taking the form of libraries, it is becoming more and more  
>> likely that
>> the important stack frame is in the middle, rather than the top or  
>> bottom,
>> of the stack.
>
>YES!  Please.
>
>-- 
>-- Jim Weirich
>-- jim.weirich / gmail.com
>
>


#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst / it.aoyama.ac.jp