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.
Product Version: NetBeans IDE Dev (Build 200809010201) Java: 1.6.0_10-rc; Java HotSpot(TM) Client VM 11.0-b14 System: Windows Vista version 6.0 running on x86; Cp1250; cs_CZ (nb) Observed: In some cases when step over expression is invoked it not only doesn't step over the expression(the session seems to be running, but also doesn't hit following breakpoints or do anything - it just seems to be running endlessly in some kind of circle) but also the threads in debugging views are flickering like crazy. Steps to reproduce: Open memory viewer sample project as main project -> make sure no breakpoints are set -> make sure MemoryView.java is set as main file -> set breakpoint on third line of main method of MemoryView.java -> invoke step into to start debugging session -> invoke step over expression twice
Created attachment 68790 [details] screenshot - just press pause after the steps and sometimes u get this
Reproduced, starting to explore what's wrong...
There are more problems: 1) Method exit breakpoint, which is submitted to get the expression return value survives finish of the debugger session and is submitted for the next debugging session. 2) Debugging view is instaneously repainted and slows down conditional breakpoints (here the above described method exit breakpoint is hit many times). Issue #145313 is submitted for this. 3) Method exit breakpoint is useless for "<init>" methods (i.e. constructors), since these have always void returned value.
Items 1) and 3) are fixed in changeset: 99769:fed90c092c88 and changeset: 99770:ffdb52ae1645 http://hg.netbeans.org/main/rev/fed90c092c88 http://hg.netbeans.org/main/rev/ffdb52ae1645 Item 2) will be fixed in issue #145313.
Integrated into 'main-golden', will be available in build *200809040201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/fed90c092c88 User: mentlicher@netbeans.org Log: #145784 - If an implementation of a hidden breakpoint is removed, remove also the breakpoint from DebuggerManager, so that the next session does not inherit it.
verified
This fix was changed in changeset: 102198:eee22cb751e2 because of issue #147321. http://hg.netbeans.org/main/rev/eee22cb751e2
Integrated into 'main-golden', will be available in build *200809170201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/eee22cb751e2 User: mentlicher@netbeans.org Log: Issue #145784 fixed in a different way - debugger-specific breakpoints introduced via JPDABreakpoint.get/setSession(). This modification of the original fix fixes issue #147321.