| Newsgroups |
gmane.comp.java.jswat.user |
| Message-ID |
<[email protected]> |
Hi all,
I posted this question yesterday but my membership hadn't
gone through yet so it was rejected - but thanks a lot for
the reply anyway Nathan! Anyway, I'm going to repost it in
hopes that maybe someone else has seen this behavior, now that it will hopefully get on the list. Nathan has added this as bug #705.
I'm running Win2000 Pro, JDK 1.4.1_01 and Jswat 2.12. I'm debugging an applet as follows:
>From the control panel /Java Plug-in/Advanced, set the JVM runtime parameters as:
-Djava.compiler=NONE -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,
address=11670 (standard stuff).
Now, start the browser (IE 6) and open the java console. This starts the vm so I can now attach to it with JSwat.
Now operate my web app to applet breakpoint.
However, when I hit my breakpoints, no local variables are
displayed. The .class files have been compiled with debugging.
Interestingly, if I simply detach JSwat and start up Forte and attach it's debugger to the JVM port and hit the breakpoint again (without restarting the browser or the JVM), I get a display of all my locals.
Since Forte can display the locals the code must have been been built correctly.
I hate to use Forte since it's so bloody slow and I like JSwat's interface better anyway but I can't for
the life of me get it to display my locals. Anyone got any ideas?
I can't dup this in appletviewer - this is a JSP app and the applet comes into play based on a series of pages which require session information so it's not a matter of simply running the one page with the applet tag. If I have time, I'll try to dup this with a simple applet on a single page and follow-up with this.
Thanks in advance for any info!
Scott Johnson
Pactolus Communication Software