MantisBT - Xdebug
View Issue Details
0001595XdebugRemote Debuggingpublic2018-12-12 13:152018-12-27 18:36
mariskay 
derick 
highblockhave not tried
resolvedunable to reproduce 
2.6.0 
 
Centos Server / Debian coding environment
7.1.0-7.1.4
0001595: Xdebug stops at breakpoint but cannot continue step by step
All was working perfectly but today after an update I cannot use Xdebug as normal. Yes, it stops @ breakpoints but cannot continue with step by step mode (f10) in VScode.

These are settings in launch.json:

        {
        "name": "Listen for XDebug",
        "type": "php",
        "request": "launch",
        "port": 9000,
        "localSourceRoot": "/home/gfxking/Desktop/CurrentDev/SCRIPTS/DEV",
        "serverSourceRoot": "/var/www/vhosts/dev/httpdocs"
    },
    {
        "name": "Launch currently open script",
        "type": "php",
        "request": "launch",
        "program": "${file}",
        "cwd": "${fileDirname}",
        "port": 9000
    }
Server output:

[root@server ~]# /opt/plesk/php/7.1/bin/php -vPHP 7.1.25 (cli) (built: Dec 7 2018 12:12:21) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.1.0, Copyright (c) 1998-2018 Zend Technologies
    with the ionCube PHP Loader (enabled) + Intrusion Protection from ioncube24.com (unconfigured) v10.2.1, Copyright (c) 2002-2018, by ionCube Ltd.
    with Zend OPcache v7.1.25, Copyright (c) 1999-2018, by Zend Technologies
    with Xdebug v2.5.0, Copyright (c) 2002-2016, by Derick Rethans
50-xdebug.ini on server:

zend_extension=xdebug.so
xdebug.default_enable=1
xdebug.remote_enable=1
xdebug.remote_autostart=1
xdebug.remote_handler=dbgp
xdebug.remote_mode=req
xdebug.remote_host=192.168.1.131
xdebug.remote_port=9000
xdebug.remote_connect_back=1
xdebug.remote_log=/var/log/xdebug.log
xdebug.profiler_enable_trigger=On
xdebug.profiler_output_dir=/tmp
xdebug.max_nesting_level=200
Maybe someone else has experienced this and knows what has suddenly changed .. today?
No tags attached.
Issue History
2018-12-12 13:15mariskayNew Issue
2018-12-23 21:07derickNote Added: 0004777
2018-12-23 21:07derickAssigned To => derick
2018-12-23 21:07derickStatusnew => feedback
2018-12-23 22:24mariskayNote Added: 0004782
2018-12-23 22:24mariskayStatusfeedback => assigned
2018-12-27 18:36derickNote Added: 0004787
2018-12-27 18:36derickStatusassigned => resolved
2018-12-27 18:36derickResolutionopen => unable to reproduce

Notes
(0004777)
derick   
2018-12-23 21:07   
I see you have the following in php.ini:
 xdebug.remote_log=/var/log/xdebug.log

Which means you have a xdebug.log file in /ar/log. Can you remove it, and then do *one* debugging session of one script? And then attach the file. Bonus points for doing this with a single script without any dependencies (including composer packages).
(0004782)
mariskay   
2018-12-23 22:24   
Please disregard this, it turned out the issue was caused my VSCode having a mysqli function in debug variable watch list. As soon as it was removed - all worked again as expected. Thanks.
(0004787)
derick   
2018-12-27 18:36   
OK, no problem. I'm closing this then.