Sylvain Joyeux wrote:
> Is there a way to remove the maximum backtrace length displayed by the
> interpreter when an exception terminates the process ? It makes the 
> backtrace
> totally useless in situations where it is long *and* the interesting 
> calls
> are in the middle.

IIRC, this only happens when the exception is handled by the top level 
interpreter.  If you catch the exception yourself at the top level you 
can print out whatever you want, including the full stack trace.

--
-- Jim Weirich

-- 
Posted via http://www.ruby-forum.com/.