This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 67619 - [50cat] Thread lock evaluting a method in the debugger
Summary: [50cat] Thread lock evaluting a method in the debugger
Status: CLOSED WONTFIX
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 5.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-26 19:38 UTC by Unknown
Modified: 2010-04-29 09:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump (22.86 KB, text/plain)
2005-10-26 19:40 UTC, Unknown 		Details
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 Unknown 2005-10-26 19:38:33 UTC 
[ BUILD # : 200510241800 ]
[ JDK VERSION : 1.5.0_05 ]

Attachment to follow
Comment 1 Unknown 2005-10-26 19:40:39 UTC 
Created attachment 26367 [details]
Thread dump
Comment 2 Roman Ondruska 2005-10-27 10:27:45 UTC 
This hang is caused by JDI bug #6293795 or it is hang in your code (e.g.:
Debuggee is stopped -> Thread A is stopped in System.out.println()--> A keeps
the 'print' lock. The method to be invoke in Thread B is waiting on the same
lock when trying to print something -> hang)
Comment 3 Unknown 2005-10-27 13:03:10 UTC 
It's not a hang in my code because it does just fine if I don't set a 
watch/breakpoint.
Comment 4 Roman Ondruska 2005-10-27 13:14:47 UTC 
Ok, I did not say this is deadlock in your code ;-)
I just said this is caused by well known JDI bug (in process, not fixable in NB)
or it can be caused by described scenario (which you can easily check).
Comment 5 Quality Engineering 2010-04-29 09:26:46 UTC 
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.