From: Hidetoshi NAGAI <nagai@...>
Date: 2003-10-17T00:59:14+09:00
Subject: Re: exception backtrace for ruby/tk programs

Hi,

From: Ferenc Engard <ferenc@engard.hu>
Subject: exception backtrace for ruby/tk programs
Date: Thu, 9 Oct 2003 08:50:56 +0900
Message-ID: <3F84A2C4.15E98C4B@engard.hu>
> I suffered with really hard debugging sessions when an unexpected
> exception was thrown from a ruby callback in a ruby/tk application, as
> the tk error dialog box showed only the error message itself and no
> backtrace. I have had to modify TkCore.callback() to reveal the
> backtrace.
> 
> Don't you miss this information? Can this be done in another way? If
> not, then here is the simple patch, maybe it can be put into the
> mainstream code.

I think the information is too verbose. So, I truncate the backtrace 
based on the difference of the backtrace between pre- and post-calling
callback-body. However, if no exception, it is waste of resources to 
get and keep the backtrace. On the CVS, I implement that the particulars 
are displayed only if $DEBUG == true. 
-- 
                                  Hidetoshi NAGAI (nagai@ai.kyutech.ac.jp)