Latest plugin version (v1.41.14263) break debugging php 5.6 with Xdebug v2.5.5
All-in-one PHP support
Colexar Thank you for reporting the issue.
May I ask for the output in DEBUG CONSOLE?
xdebug console output: invalid or missing options
Colexar thank you,
Just to be sure, here you have PHP 5.4 and Xdebug 2.5.5?
Thank you. I think we know what caused it now. We'll fix it.
Clarification: 1.41.14263 is the latest plugin version than work for me.
PHP Version 5.6.40 with Xdebug v2.5.5
PHP API 20131106
PHP Extension 20131226
Zend Extension 220131226
Zend Extension Build API220131226,NTS
PHP Extension Build API20131226,NTS
Confirm, I have the same issue.
PHP 5.6.40
PHP API 20131106
PHP Extension 20131226
Zend Extension 220131226
Zend Extension Build API220131226,NTS
PHP Extension Build API20131226,NTS
VSCode debug console:
Listening to Xdebug on port 0.0.0.0:9011,:::9011 ...
invalid or missing options
xdebug.log:
Log opened at 2023-12-11 06:10:25
I: Connecting to configured address/port: host.docker.internal:9011.
I: Connected to client. :-)
-> <init xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" fileuri="file:///app/index.php" language="PHP" xdebug:language_version="5.6.40" protocol_version="1.0" appid="9" idekey="daemon"><engine version="2.5.5"><![CDATA[Xdebug]]></engine><author><![CDATA[Derick Rethans]]></author><url><![CDATA[http://xdebug.org]]></url><copyright><![CDATA[Copyright (c) 2002-2017 by Derick Rethans]]></copyright></init><- feature_set -i 1 -n max_children -v 100
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="feature_set" transaction_id="1" feature="max_children" success="1"></response><- feature_set -i 2 -n max_data -v 8192
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="feature_set" transaction_id="2" feature="max_data" success="1"></response><- feature_set -i 3 -n notify_ok -v 1
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="feature_set" transaction_id="3" status="starting" reason="ok"><error code="3"><message><![CDATA[invalid or missing options]]></message></error></response><- stop -i 4
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="stop" transaction_id="4" status="stopped" reason="ok"></response>
Thank you! This is now handled. The next pre-release shouldn't report the warning.