On 1 Feb 2006, at 20:34, Mo DeJong wrote:

>  On Wed, 1 Feb 2006 12:29:06 +0200 (EET)
>  Kristoffer Lawson <setok@[...].com> wrote:
> 
> >
> > The current release version of jaclsh does not seem to give a  
> > stack trace
> > on an error. Is there some obvious way to remedy this which I have  
> > missed?
> > If not, will such a feature be appearing in future versions?
> 
>  Need more info. Are you talking about a Tcl stack trace via the  
>  errorInfo
>  variable? Or are you talking about a Java stack trace from an  
>  unhandled
>  exception in the main() thread? As far as I know, both of these work
>  in the general case. There are some cases where one method or another
>  might catch exceptions and not print them, if you could provide some
>  specifics about the situation that would really help.

A Tcl stack trace. I ran a script with jaclsh and an error was given,  
but the usual stack trace was not given.

            /  http://www.fishpool.com/~setok/



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
tcljava-user mailing list
tcljava-user@[...].net
https://lists.sourceforge.net/lists/listinfo/tcljava-user