Skip to main content



      Home
Home » Language IDEs » Java Development Tools (JDT) » Deadlock indication in debugger
Deadlock indication in debugger [message #254125] Sat, 21 June 2008 12:26
Eclipse UserFriend
Originally posted by: laurens.vanhels.telenet.be

Hi,

If someone could point me to some advanced debugger material explaining
the following.. I'd be very grateful.

When trying to debug my multithreaded app, I can see that the debugger
eliminates much guesswork by indicating (with red highlights) that I've
got a number of threads deadlocked. What I don't understand is that the
"Waiting for" indication of the culprit "int[][]" lock says that it is
owned by Thread X, yet when I scan that Thread's stack frame, I can not
see the spot where such a 2-D int array would become locked.

Another thing that bugs me is object ids.. this "int[][]" has an id, but
what can the debugger do with this id? Is there any way I could ask it to
show me all objects, sorted by id, which apparently is allocated
chronologically? That way, I could maybe discover what instantiated that
2-D array...

Thx.

PS. I'm still on 3.2 Eclipse. Hope I'm not going to get flamed with "Use
the 3.3 debugger and your problem will go away.."
Previous Topic:eporting runnable jar with mail api
Next Topic:Re: target 1.5 in eclipse
Goto Forum:
  


Current Time: Sat Jun 07 14:00:22 EDT 2025

Powered by FUDForum. Page generated in 0.13470 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top