Re: Debugging Java 1.4 API with JSwat?

I'll look into the GUI speed problem. Maybe it's time for RFE #429:
manual refresh mode for some (or all) panels. This would dramatically
reduce the overhead, but it would mean an inconvenience for the user.
Obviously this would have to be an option.

BTW, this reminds me of the occasional profiler requests. While I do not
like the idea of integrating profiler features into JSwat, I would be
interested in starting a separate profiler project.

Oh, one other thing. Did you try remotely debugging the application?
That is, start it with the JPDA flags (suspend=n) and let it finish
loading. Then attach JSwat and start debugging. That would probably help
since the debuggee classes would all have loaded by the time JSwat
attaches.

n


On Mon, 2002-05-06 at 13:35, Paul Legato wrote:
> 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