Bug 81423 - Missing information when deadlock is resolved
Summary: Missing information when deadlock is resolved
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-16 11:49 EST by Jerome Lanneluc CLA
Modified: 2004-12-16 12:21 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jerome Lanneluc CLA 2004-12-16 11:49:47 EST 
I20041216

Bug 81306 shows a stack trace saying that a deadlock occured during start up. It
looks like the deadlock was resolved, but the trace doesn't provide enough
information to debug this problem.

It should at least show:
- the classes that were being loaded at the time of the deadlock
- the stacks of all the threads at the time of the deadlock
Comment 1 Pascal Rapicault CLA 2004-12-16 12:02:05 EST 
The message is providing all the info that are available at that time...

The class that is being loaded and that caused the message is indicated in the
message (for example in the bug you mentionned, it is
org.eclipse.jdt.core.JavaCore$7).

Showing the stack of all the thread is impossible in that case since Java does
not expose API that allow it (Thread.dumpStack() applies to the current thread).
If you know a trick then we'd happy to hear it because we are not really happy
with the current state of this message.
Comment 2 Jerome Lanneluc CLA 2004-12-16 12:05:52 EST 
Thread#getThreadGroup() is your friend.
Comment 3 Pascal Rapicault CLA 2004-12-16 12:10:36 EST 
I'm not sure what to do then, how do I get their stack trace?
Comment 4 Jerome Lanneluc CLA 2004-12-16 12:21:29 EST 
Sorry, I looked at 1.5 API which you cannot rely on. Agreed that there is
nothing you can do.