Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 356583

Summary: DeadlockDetector should log stack traces of all involved threads
Product: [Eclipse Project] Platform Reporter: Anton Leherbauer <aleherb+eclipse>
Component: RuntimeAssignee: platform-runtime-inbox <platform-runtime-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: remy.suen, tjwatson, yevshif
Version: 3.7   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: stalebug
Attachments:
Description Flags
Get stack trace using reflection none

Description Anton Leherbauer CLA 2011-09-02 09:00:26 EDT 
If a deadlock is detected, currently only the stack trace of the current thread is logged, but for further analysis it would be very helpful to have stack traces of all involved threads.

Unfortunately Thread#getStackTrace() is only available since 1.5, so this would require either the use of reflection or moving org.eclipse.core.runtime to 1.5.
Comment 1 John Arthorne CLA 2011-09-02 11:43:43 EDT 
Another option would be to use reflection.
Comment 2 Anton Leherbauer CLA 2011-09-06 07:21:58 EDT 
Created attachment 202796 [details]
Get stack trace using reflection

This works for me.
Comment 3 Lars Vogel CLA 2019-11-14 03:35:14 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.