From: Mark Brown <email@hidden>
> In a previous post, I talked about our JComboBox problem, where at times the cursor will turn
> into a permanent pinwheel and hang the application. We can't seem to reproduce the problem while > running through the debugger.
> I was wondering...is there a way to make the application crash at this point so a java.crash.log > can be generated, that will tell us which thread is hung?
> I tried using "kill -6 PID" (-6 is ABORT), but no log was generated.
Launching command line from terminal is whats supposed to allow the ctrl+\ stack crawls I think. Launching the application this way might make it more responsive to the kill signal. Isn't kill -QUIT whats supposed to actually get you a current stack crawl? Unless thats same as -6 I'm not sure on that either.
There were some odds and ends in the developer tools install. This included some process watcher and I think killer that might work.
Other than IDE's there are other possibly other debuggers and ways to run them. Although in some cases they might end up amounting to the same thing that being the java debugging built in stuff. You could try running the application from gdb. Or with jdb. As an IDE'less GUI'd java debugger interface JSwat is kind of nice.
Mike Hall mikehall at spacestar dot net
http://www.spacestar.net/users/mikehall
_______________________________________________
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
This email sent to email@hidden
