Something that is useful in this situation is to attach with gdb, and
get both the native and the java stacks.
gdb
attach java.<pid>
t a a bt
call (void)pss()
the "t a a bt" will get a stacktrace of all native threads
the "call (void)pss()" will dump a stacktrace of all java threads to
wherever the java app was launched from (probably Terminal), or
Console, if launched as a .app.
Karl
On Sep 30, 2004, at 9:00 AM, Mark Brown wrote:
Hi-
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.
Just looking for another way to find out what is causing the problem.
Thanks,
Mark
---
Mark Brown, Senior Software Engineer
Innovative Software Engineering
Technology Innovation Center
100 Oakdale Campus, #101 TIC
Iowa City, IA 52242
"The difference between ordinary and extraordinary is that little
extra"
_______________________________________________
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
--
Test Question from Topanga Cabal, The Twelve Famous Buddha Minds School:
"If they are our brothers, why can we not eat them?"
_______________________________________________
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
