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 258826 - XDebug breaks after hit F8 for jump over
Summary: XDebug breaks after hit F8 for jump over
Status: RESOLVED WORKSFORME
Alias: None
Product: php
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 8.1
Hardware: PC Windows 10 x64
: P2 normal (vote)
Assignee: Tomas Mysik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-14 12:05 UTC by Christian Lenz
Modified: 2016-05-27 12:59 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Lenz 2016-04-14 12:05:20 UTC
I configured the Xdebug in the xdebug.ini on a remote host, I configured the xdebug inside netbeans and everything is fine, it breaks at a setted breakpoint in a method. After I hit F8 for jump over instructions, I got a Socket Exception as a dialog and when I have a look in the IDE.log I saw this:


INFO [org.netbeans.modules.php.dbgp.DebugSession]
java.net.SocketException: Software caused connection abort: socket write error
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:141)
	at org.netbeans.modules.php.dbgp.packets.DbgpCommand.send(DbgpCommand.java:92)
	at org.netbeans.modules.php.dbgp.DebugSession.sendCommands(DebugSession.java:208)
[catch] at org.netbeans.modules.php.dbgp.DebugSession.run(DebugSession.java:140)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

I tried IntelliJ and everything is fine. Config works as expected, breaks at point as expected. Jump over doesn't work and breaks the Debug session.


Regards

Chris
Comment 1 Tomas Mysik 2016-05-27 12:15:45 UTC
This means some local network error, see e.g. [1] or [2]. Unfortunately, I am not sure whether we can do something here if we cannot reproduce this issue... so, does it happen always? With all your PHP projects? Would it be possible to attach a sample project? Are you debugging a web page or CLI script? Do you have latest Xdebug installed? Could you please enable Xdebug logging [3], reproduce the problem and attach the log here?

I just tried to debug a CLI script and it works for me without any problem in dev version of NetBeans. My PHP version can be found below.

Please, reopen this issue and provide information we need.

Thank you for your cooperation.

[1] https://msdn.microsoft.com/en-us/library/ms832256.aspx
[2] https://community.oracle.com/thread/1691330
[3] http://wiki.netbeans.org/HowToConfigureXDebug#Enable_Xdebug_logging

Product Version: NetBeans IDE Dev (Build 20160527-fd8f61fc249e)
Java: 1.8.0_91; Java HotSpot(TM) 64-Bit Server VM 25.91-b14
Runtime: Java(TM) SE Runtime Environment 1.8.0_91-b14
System: Linux version 4.2.0-36-generic running on amd64; UTF-8; cs_CZ (nb)

PHP 5.5.9-1ubuntu4.17 (cli) (built: May 19 2016 19:05:57) 
Copyright (c) 1997-2014 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2014 Zend Technologies
    with Zend OPcache v7.0.3, Copyright (c) 1999-2014, by Zend Technologies
    with Xdebug v2.4.0, Copyright (c) 2002-2016, by Derick Rethans
Comment 2 Christian Lenz 2016-05-27 12:47:57 UTC
It is my only PHP project at my company atm. It is a webapplication hosted on a remote host. So It's not hosted locally on my machine, only the code and I remote debug it. As I wrote in IntelliJ or PHPStorm, everyting was fine. I don't know whether it is the latest version of xdebug or not. I will check it later if I have to debug it again, what can happen ^^. So I don't think that this is smth from my machine, in my opinion. Maybe a config problem for example with the remote host communication.
Comment 3 Tomas Mysik 2016-05-27 12:59:07 UTC
Thanks for the information. Unfortunately, java.net.SocketException is not always clear and easy to fix. It would be great if you could provide the Xdebug log (see my previoud comment how to enable it).

Thanks for your cooperation.