tcljava-user

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

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

 > Are there any recommended debuggers for jacl and instructions on how 
to use them?

Patrick

I use JSwat, but you should be able to use any Java debugger that works 
with the JPDA. All
you need to do at runtime is set JACL_DEBUG=1 before launching jtclsh. 
That will add the
src jars to the CLASSPATH so that you can step through Jacl code in the 
debugger. If you
want to debug TJC generated Java code you can also do that by compiling 
Tcl procs into
Java source and then you can step through the Java source a line at a time.

cheers
Mo DeJong

P.S.
Patrick, please don't post messages to this list that include junk 
footers like
"This email is confidential blah blah blah". The terms of use for this
mailing list clearly state that these type of claims are not allowed.

http://tcljava.sourceforge.net/docs/website/mail.html

You risk being booted off the list by posting message like that.

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

[Patrick F. <pfi...@oz...>]

On Sunday 14 January 2007 02:23, Mo DeJong wrote:
>  > Are there any recommended debuggers for jacl and instructions on how
>
> to use them?
>
>

I had a quick look at Jswat but since we are using Eclipse as the standard
IDE I tried it's remote debug facility. =A0Eclipse connects to the remote
JACL JVM all right and I was able to walk through tcl.lang.Shell by importi=
ng=20
the source code into the project and setting a breakpoint.  But of course=20
what I need to do is set breakpoints in JACL code not the underlying java=20
stuff.  Is there a way to do this?

Thinking about this further one might run one of the existing TK debuggers=
=20
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=
=20
either required 8.1 or greater or Tcl packages that have not been ported to=
=20
JACL.

Any ideas? =20

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