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.
Thanks
Sylvain
Hi,
In message "Re: Length of backtrace displayed by ruby" on Wed, 5 Apr 2006 00:25:52 +0900, Sylvain Joyeux <sylvain.joyeux@polytechnique.org> writes:
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.
Not yet. Do you (or anybody else) have any good API suggestion?
matz.
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.
Exception.backtrace_display_limit = 42
??
-a
On Wed, 5 Apr 2006, Yukihiro Matsumoto wrote:
Hi,
In message "Re: Length of backtrace displayed by ruby" > on Wed, 5 Apr 2006 00:25:52 +0900, Sylvain Joyeux <sylvain.joyeux@polytechnique.org> writes:
>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.Not yet. Do you (or anybody else) have any good API suggestion?
matz.
--
share your knowledge. it's a way to achieve immortality.
- h.h. the 14th dali lama
Yukihiro Matsumoto <matz@ruby-lang.org> writes:
Hi,
>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.Not yet. Do you (or anybody else) have any good API suggestion?
matz.
How about giving a full backtrace with ruby -d?
In message "Re: Length of backtrace displayed by ruby" > on Wed, 5 Apr 2006 00:25:52 +0900, Sylvain Joyeux <sylvain.joyeux@polytechnique.org> writes:
--
Christian Neukirchen <chneukirchen@gmail.com> http://chneukirchen.org
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.
Yes, that's what I did as a workaround. But you have to do it for every
thread and every fork (which in my case is 4 different places)
--
Sylvain Joyeux
Exception.setFilter(regularExpression)
where the matching items are removed from the backtrace.
Stephen
In message <Pine.LNX.4.62.0604040944090.5852@harp.ngdc.noaa.gov>, ara.t.howard@noaa.gov writes
On Wed, 5 Apr 2006, Yukihiro Matsumoto wrote:
Not yet. Do you (or anybody else) have any good API suggestion?
Exception.backtrace_display_limit = 42
--
Stephen Kellett
Object Media Limited http://www.objmedia.demon.co.uk/software.html
Computer Consultancy, Software Development
Windows C++, Java, Assembler, Performance Analysis, Troubleshooting
what would be matched?
e.to_s, e.message.to_s, or e.backtrace.any?{|b|}
regards.
-a
On Wed, 5 Apr 2006, Stephen Kellett wrote:
In message <Pine.LNX.4.62.0604040944090.5852@harp.ngdc.noaa.gov>, > ara.t.howard@noaa.gov writes
On Wed, 5 Apr 2006, Yukihiro Matsumoto wrote:
Not yet. Do you (or anybody else) have any good API suggestion?
Exception.backtrace_display_limit = 42
Exception.setFilter(regularExpression)
where the matching items are removed from the backtrace.
--
share your knowledge. it's a way to achieve immortality.
- h.h. the 14th dali lama
Class and method name was what I was thinking of.
In message <Pine.LNX.4.62.0604041611040.5852@harp.ngdc.noaa.gov>, ara.t.howard@noaa.gov writes
Exception.setFilter(regularExpression)
where the matching items are removed from the backtrace.
what would be matched?
e.to_s, e.message.to_s, or e.backtrace.any?{|b|}
--
Stephen Kellett
Object Media Limited http://www.objmedia.demon.co.uk/software.html
Computer Consultancy, Software Development
Windows C++, Java, Assembler, Performance Analysis, Troubleshooting