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.
Nevada 030408, JDK1.4.1_02, MDI. 1. Download attached test case. 2. Mount it in the IDE (no package). 3. Start debugging of this class (Debug/Start Session/Run in Debugger) (do not set any breakpoints, the testcase is an infinite loop). 4. Start it again. Choose "Start New Session". 5. In the sessions view, choose "Finish" on the second session. Attached NullPointerException will occur. Note: Although the steps to reproduce run the same class twice, it is not necessary. The same problem occurs when debugging two different applications, even if one or both of them are "Attached".
Created attachment 9843 [details] Test class.
Created attachment 9844 [details] Stack trace of the NullPointerException.
fixed in trunk
Created attachment 9866 [details] patch file
Can you provide a diff file for review? Thanks.
Verified - I used an attached patch in the S1S build 030409 and it see ms that this problem disappeared.
fix is trivial -> merging to release35 RCS file: /cvs/debuggercore/src/org/netbeans/modules/debugger/support/IOManager.java,v retrieving revision 1.18 diff -r1.18 IOManager.java 264,265c264,267 < debuggerIO.setOutputVisible (visible); < processIO.setOutputVisible (visible); --- > if (debuggerIO != null) > debuggerIO.setOutputVisible (visible); > if (processIO != null) > processIO.setOutputVisible (visible);
Verified in Nevada 030414.