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.
This issue was reported manually by vv159170. It already has 1 duplicates Build: NetBeans IDE 7.3 Beta 2 (Build 201211062253) VM: Java HotSpot(TM) 64-Bit Server VM, 23.0-b21, Java(TM) SE Runtime Environment, 1.7.0_04-b22 OS: Windows 7 Stacktrace: java.io.IOException: Channel is already closed at org.netbeans.modules.nativeexecution.JschSupport$ProtectedOutputStream.checkAlive(JschSupport.java:249) at org.netbeans.modules.nativeexecution.JschSupport$ProtectedOutputStream.flush(JschSupport.java:235) at org.netbeans.modules.cnd.debugger.common2.debugger.io.IOProxy$InputWriterThread.run(IOProxy.java:165)
Created attachment 128967 [details] stacktrace
fixed in http://hg.netbeans.org/cnd-main/rev/b149f5869bef
Integrated into 'main-golden', will be available in build *201212080001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/b149f5869bef User: Maria Tishkova <mromashova@netbeans.org> Log: fixed bz#223403 java.io.IOException: Channel is already closed there is no need to print exception on flush/close in finally if it is not printed out when we cannot write in the stream