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 80477 - Deadlock when printing local variable on breakpoint hit
Summary: Deadlock when printing local variable on breakpoint hit
Status: VERIFIED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-18 13:28 UTC by Jiri Kovalsky
Modified: 2006-10-23 16:39 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Project reproducing debugger deadlock. (8.11 KB, application/x-compressed)
2006-07-18 13:29 UTC, Jiri Kovalsky 		Details
Thread dump showing the deadlock. (2.99 KB, text/plain)
2006-07-18 13:30 UTC, Jiri Kovalsky 		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 Jiri Kovalsky 2006-07-18 13:28:45 UTC 
Beta 2 build #200607180300 of NetBeans 5.5
Windows XP, JDK 1.5.0_02 build #09

Description:
============
I have found a scenario that always deadlocks IDE. This happens when line
breakpoint is customized in order to print local method variable. When the
breakpoint is hit it is only necessary to "Continue" in debugging. Debugger gets
into strange state and if user tries to delete the breakpoint, IDE freezes. The
scenario is 100% reproducible with the attached project.

Steps to reproduce:
===================
1. Extract attached project somewhere and open it in the IDE.
2. Open "QuizTest_1|Source Packages|quiztest|QuizTest.java" class in editor.
3. Toggle breakpoint (Ctrl+F8) at line 34.
4. Invoke "Window|Debugging|Breakpoints" (Alt+Shift+5) from main menu.
5. Right click "Line QuizTest.java:34" breakpoint and choose "Customize".
6. Set "Print Text:" field to "Value of magicNumber is {=magicNumber}." text.
7. Push "OK" button and invoke "Run|Debug Main Project" (F5) from main menu.
8. When breakpoint is hit, invoke "Run|Continue" (Ctrl+F5) from main menu.
9. Note that the same breakpoint is not hit anymore !
10. Right click "Line QuizTest.java:34" breakpoint and choose "Delete".
Comment 1 Jiri Kovalsky 2006-07-18 13:29:48 UTC 
Created attachment 31958 [details]
Project reproducing debugger deadlock.
Comment 2 Jiri Kovalsky 2006-07-18 13:30:30 UTC 
Created attachment 31959 [details]
Thread dump showing the deadlock.
Comment 3 Jiri Kovalsky 2006-07-18 13:34:32 UTC 
Please note this is not a regression i.e. it is also present in NetBeans 5.0.
Comment 4 Martin Entlicher 2006-07-18 15:54:53 UTC 
This can not be reproduced in dev builds => It was already fixed, I'm searching
for when was the fix applied...
Comment 5 Martin Entlicher 2006-07-18 15:56:45 UTC 
It was issue #50811, whose fix also fixed this deadlock.

cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/JPDADebuggerImpl.java,v
 <--  JPDADebuggerImpl.java
new revision: 1.100; previous revision: 1.99

Therefore it's fixed in trunk.
Comment 6 Jiri Kovalsky 2006-07-19 08:08:59 UTC 
Oh yes, you are right ! Sorry, I didn't find the duplicate issue. Verifying in
development build #200607181800 of NetBeans 6.0.