Re: Debugging Java 1.4 API with JSwat?

Hi Nathan,

I checked, and the "Methods" and "Locals" lists do populate on a stopped 
thread.

I also gave it a try in console mode, and the application runs at 
(almost) full speed. A huge difference from GUI mode, very dramatic 
speed improvement.

I'll run with that for now.. thanks for the information. :)

-Paul


Nathan Fiedler wrote:

>Is the thread suspended when you make it the current thread? The locals
>and methods panel can't show anything while the thread is running. If it
>is suspended, then I don't know what to tell you. JSwat gets all of its
>information from the JPDA and if it reports an exception, there's
>nothing JSwat can do.
>
>If JSwat seems slow, give it a try in console mode (add the -console
>switch when starting jswat) and let me know if that helps significantly.
>If not, then there's not much I can do about it. Debugging does have a
>tendency to slow things down. But if JSwat is making it worse, I'd like
>to know.
>
>And supposedly the 1.4 HotSpot VM has "Full-Speed" debugging, so maybe
>it's time I alter that FAQ answer.
>
>n
>
>
>On Mon, 2002-05-06 at 13:08, Paul Legato wrote:
>
>>Hi,
>>I've got a Swing application that makes heavy use of new 1.4 classes, 
>>and a nasty bug where a private variable that is only ever assigned to 
>>in the constructor is somehow re-setting itself to null at some point. 
>>When I load it into JSwat for debugging, it runs very slowly. Very, 
>>very, very slowly..
>>
>> Also, when I click on a thread, I get "(bad thread state)" in the 
>>Methods and Locals panels.
>>
>>I gather from the FAQ that these sorts of problems are caused by use of 
>>the HotSpot VM. Unfortunately, Java 1.4 no longer includes the classic VM.
>>
>>Are there any options I'm missing that'll allow me to debug with 1.4?
>>
>>Thanks,
>>-Paul
>>
>
>
>_______________________________________________
>jswat-user mailing list
>[email protected]
>http://www.bluemarsh.com/mailman/listinfo/jswat-user
>