Re: [tcljava-user] JACL - Which Java Debugger?

[Mo D. <mo...@mo...>]

Patrick Finnegan wrote:
> I had a quick look at Jswat but since we are using Eclipse as the standard
> IDE I tried it's remote debug facility.  Eclipse connects to the remote
> JACL JVM all right and I was able to walk through tcl.lang.Shell by importing 
> the source code into the project and setting a breakpoint.  But of course 
> what I need to do is set breakpoints in JACL code not the underlying java 
> stuff.  Is there a way to do this?
>   
Yes, you can compile the Tcl code into Java code using TJC and then step 
through the compiled code
in a Java debugger. It is really quite easy to do and the generated Java 
source is easy to understand.
> Thinking about this further one might run one of the existing TK debuggers 
> under Swank.  Say something like this:
>
> c:> java tcl.lang.Swank debugger.tcl yourScript.tcl.
>
> However Swank/JACL only supports Tcl 8.0 and most of the debuggers I tried 
> either required 8.1 or greater or Tcl packages that have not been ported to 
> JACL

It depends on what features the Tcl debuggers use. If they just run 
"package require Tcl 8.1" then
just change it to 8.0 and see if everything works as expected. Jacl is 
really more like Tcl 8.4 at
this point, except for some regexp and non-blocking io issues.

Mo DeJong