Which actually is one I was using a number of times the last couple
of days.
Then I would use JSwat to attach a remote debug session that would
allow me to get stack traces, breakpoints, etc.
(I use an older version of JSwat, newer versions seem too tied to
NetBeans for me to be able even to figure out how to run it).
If its simple enough you just use the jvm command line sample
debugger tool jdb.
Something like...
jdb -classpath .:quaqua-filechooser-only.jar ChooserFrame
Initializing jdb ...
> run
run ChooserFrame
Set uncaught java.lang.Throwable
Set deferred uncaught java.lang.Throwable
>
VM Started:
Looking at local variables didn't seem to work this way while it did
with JSwat so you might find some reason you prefer one way over the
other.
NetBeans might again have too complicated a start up to do this, and
of course usually I think this is the sort of thing you want a IDE
for. Not the sort of thing you want to use on a IDE.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
