That works - thanks! Now we just wait for it to hang again. :)
-----Original Message-----
From: java-dev-bounces+markbrown=email@hidden
[mailto:java-dev-bounces+markbrown=email@hidden] On Behalf Of
email@hidden
Sent: Thursday, September 30, 2004 11:46 AM
To: email@hidden
Subject: Re: Can you crash a Java App to generate java.crash.log?
Mark Brown wrote:
| 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.
I'm not much surprised. "SIGABRT" is generated when a program commits
voluntary suicide, by calling the abort() routine. That generally doesn't
count as a "crash". Me, I'd try a signal that actually says things are
broken: SIGILL (4-illegal instruction) or SIGBUS (10-bus error [illegal
memory address]).
You might also do "kill -QUIT" first, which will cause the JVM to produce a
full set of stack traces (one for each thread), written to the standard
output (which is the console log for bundled applications).
Glen Fisher
_______________________________________________
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
