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.
Build: NetBeans IDE 6.5 Beta (Build 200808111757) VM: Java HotSpot(TM) Client VM, 10.0-b23, Java(TM) SE Runtime Environment, 1.6.0_07-b06 OS: Windows XP, 5.1, x86 User Comments: Stacktrace: java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(SocketOutputStream.java:0) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:124) at org.netbeans.modules.php.dbgp.packets.DbgpCommand.send(DbgpCommand.java:84) at org.netbeans.modules.php.dbgp.DebugSession.sendCommands(DebugSession.java:241) at org.netbeans.modules.php.dbgp.DebugSession.run(DebugSession.java:88)
Created attachment 69474 [details] stacktrace
Build: NetBeans IDE Dev (Build 200809120201) VM: Java HotSpot(TM) 64-Bit Server VM, 10.0-b23, Java(TM) SE Runtime Environment, 1.6.0_07-b06 OS: Linux, 2.6.26, amd64 User Comments: using XDebug to step through PHP code Stacktrace: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(SocketOutputStream.java:0) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:124) at org.netbeans.modules.php.dbgp.packets.DbgpCommand.send(DbgpCommand.java:84) at org.netbeans.modules.php.dbgp.DebugSession.sendCommands(DebugSession.java:242) at org.netbeans.modules.php.dbgp.DebugSession.run(DebugSession.java:88)
Created attachment 69776 [details] stacktrace
Build: NetBeans IDE Dev (Build 200809120201) VM: Java HotSpot(TM) 64-Bit Server VM, 10.0-b23, Java(TM) SE Runtime Environment, 1.6.0_07-b06 OS: Linux, 2.6.26, amd64 User Comments: setting watched variable while debugging PHP with XDebug Stacktrace: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(SocketOutputStream.java:0) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:124) at org.netbeans.modules.php.dbgp.packets.DbgpCommand.send(DbgpCommand.java:84) at org.netbeans.modules.php.dbgp.DebugSession.sendCommands(DebugSession.java:242) at org.netbeans.modules.php.dbgp.DebugSession.run(DebugSession.java:88)
Created attachment 69791 [details] stacktrace
Build: NetBeans IDE Dev (Build 200809071401) VM: Java HotSpot(TM) Client VM, 10.0-b19, Java(TM) SE Runtime Environment, 1.6.0_05-b13 OS: Linux, 2.6.18-92.1.10.el5, i386 User Comments: php debug a source file (not project) Stacktrace: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(SocketOutputStream.java:0) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:124) at org.netbeans.modules.php.dbgp.packets.DbgpCommand.send(DbgpCommand.java:84) at org.netbeans.modules.php.dbgp.DebugSession.sendCommands(DebugSession.java:242) at org.netbeans.modules.php.dbgp.DebugSession.run(DebugSession.java:88)
Created attachment 69813 [details] stacktrace
Build: NetBeans IDE Dev (Build 200809071401) VM: Java HotSpot(TM) Client VM, 10.0-b19, Java(TM) SE Runtime Environment, 1.6.0_05-b13 OS: Linux, 2.6.18-92.1.10.el5, i386 User Comments: Starting PHP debug session Stacktrace: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(SocketOutputStream.java:0) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:124) at org.netbeans.modules.php.dbgp.packets.DbgpCommand.send(DbgpCommand.java:84) at org.netbeans.modules.php.dbgp.DebugSession.sendCommands(DebugSession.java:242) at org.netbeans.modules.php.dbgp.DebugSession.run(DebugSession.java:88)
Created attachment 69814 [details] stacktrace
Seems like a bug in xdebug or its clone: http://bugs.xdebug.org/bug_view_page.php?bug_id=0000313 If I'm right, then the workaround should be to delete all watches: - open watches window - menu Window-> Debugging->watches - delete all watches - in popup menu action "Delete All" At least one user confirmed this workaround helped. Anyway better error handling in NB is needed.
Agree rmatous:rmatous@netbeans.org assumption as restarting netbeans and removing watches stopped to exception <quote>Seems like a bug in xdebug or its clone: http://bugs.xdebug.org/bug_view_page.php?bug_id=0000313 If I'm right, then the workaround should be to delete all watches: - open watches window - menu Window-> Debugging->watches - delete all watches - in popup menu action "Delete All" At least one user confirmed this workaround helped. Anyway better error handling in NB is needed.</quote> better handling of this exception recommended (even a pop up notice of invalid watch or something would be better)
Increasing to P2 because of many duplicates.
Workaround pushed to the trunk. http://hg.netbeans.org/main/rev/b4d9d15738a6
Integrated into 'main-golden', will be available in build *200810031942* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/b4d9d15738a6 User: Tomas Mysik <tmysik@netbeans.org> Log: #146724: java.net.SocketException: Software caused connection abort: socket write error
*** Issue 149620 has been marked as a duplicate of this issue. ***
reopening as P4 just as reminder of xdebug problem
Reassigning to the owner of subcomponent.
*** Issue 155687 has been marked as a duplicate of this issue. ***
*** Issue 158945 has been marked as a duplicate of this issue. ***
batch reassigning
I created a new xdebug issue, because the old one was "fixed"...but it still doesn't work. So new issue is here: http://bugs.xdebug.org/view.php?id=704
My new issue was marked as a duplicate of another issue which was somehow solved and needs feedback (http://bugs.xdebug.org/view.php?id=606). There is a patch which should fix it so don't hesitate to try it and let Derick know if it really works. Closing this as incomplete.
Should be fixed in XDebug 2.1.3 and 2.2dev. (http://bugs.xdebug.org/view.php?id=704#c1779)