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 22795 - Debugger freezed - breakpoint reached during evaluation of expression
Summary: Debugger freezed - breakpoint reached during evaluation of expression
Status: VERIFIED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P2 blocker with 1 vote (vote)
Assignee: issues@debugger
URL:
Keywords: ARCH
Depends on:
Blocks:
 
Reported: 2002-04-25 14:43 UTC by pgodeau
Modified: 2005-07-13 11:33 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
full thread dump (16.70 KB, text/plain)
2004-05-05 12:38 UTC, Milan Kubec 		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 pgodeau 2002-04-25 14:43:54 UTC 
It is very easy to block the debugger with the
following code. Just set the breakpoints, and
select "test ()" in the code to see the value in a
tool tip. The debugger goes to the line "return
12" then it is freezed.

----8<----8<----

class DebugTest {
  private static int test () {
    return 12; // breakpoint
  }
  public static void main (String[] args) {
    System.out.println (test ()); // breakpoint +
select
  }
}
Comment 1 Marek Grummich 2002-05-06 10:14:36 UTC 
I can confirm a described behaviour. I see it on my Linux in build FFJ
020501_1.
Comment 2 Jan Jancura 2002-05-09 10:24:43 UTC 
accepted by dev.
Comment 3 Marek Grummich 2002-07-22 09:04:02 UTC 
Target milestone was changed from '3.4' to TBD.
Comment 4 Marek Grummich 2002-07-22 09:08:05 UTC 
Target milestone was changed from '3.4' to TBD.
Comment 5 David-john Burrowes 2002-10-16 22:37:23 UTC 
From conversations held recently on things like this, We decided that
tooltips should not be generated from method calls in the code  (that
is, methods should only be invoked from things like the watches.
Comment 6 Jan Jancura 2003-02-13 12:46:09 UTC 
Behaviour described by user is fixed in the main trunk.
Comment 7 Jan Jancura 2003-06-27 10:15:45 UTC 
The problen is still reproducible - probably mistake.
Comment 8 Maros Sandor 2004-01-07 10:55:21 UTC 
Will be fixed in 3.6.
Comment 9 Maros Sandor 2004-01-13 09:09:52 UTC 
Fixing this issue would require considerable debugger re-design => 
promo-D.
Comment 10 Milan Kubec 2004-02-05 10:20:43 UTC 
Removing fix-in-36 if it's planed for promo-D.
Comment 11 Milan Kubec 2004-05-05 12:37:32 UTC 
Debugger has been redesigned and this issue's still there. Whole IDE
is frozen. I will attach thread dump.
Comment 12 Milan Kubec 2004-05-05 12:38:07 UTC 
Created attachment 14725 [details]
full thread dump
Comment 13 Jan Jancura 2004-05-23 20:05:52 UTC 
fixed in the main trunk
Checking in src/org/netbeans/modules/debugger/jpda/JPDADebuggerImpl.java;
/cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/JPDADebuggerImpl.java,v
 <--  JPDADebuggerImpl.java
new revision: 1.32; previous revision: 1.31
done
Comment 14 Max Sauer 2005-07-13 11:33:10 UTC 
Verified in nbdev200507110943.