Hi,

I can reproduce it, but it is not a bug. The DBGp protocol originally did not expect there to be NULL characters in class names, but PHP does use this. This situation can be handled to enable the ("extended_properties")[https://xdebug.org/docs/dbgp#extended-properties] feature. When enabling this with:

feature_set -n extended_properties -v 1

Valid XML is returned:

<?xml version="1.0" encoding="iso-8859-1"?>

<init xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" fileuri="file:///home/derick/dev/php/derickr-xdebug/tests/debugger/bug02025.inc" language="PHP" xdebug:language_version="8.1.4-dev" protocol_version="1.0" appid="2226691" idekey="yes"><engine version="3.1.4-dev"><![CDATA[Xdebug]]></engine><author><![CDATA[Derick Rethans]]></author><url><![CDATA[https://xdebug.org]]></url><copyright><![CDATA[Copyright (c) 2002-2022 by Derick Rethans]]></copyright></init>

DBGp/1.0: Xdebug 3.1.4-dev — For PHP 8.1.4-dev

Debugging file:///home/derick/dev/php/derickr-xdebug/tests/debugger/bug02025.inc (ID: 2226691/yes)

(cmd) feature_set -n extended_properties -v 1

<?xml version="1.0" encoding="iso-8859-1"?>

<response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" command="feature_set" transaction_id="1" feature="extended_properties" success="1"></response>

1 | feature_set

1 | extended_properties: OK

(cmd) run

<?xml version="1.0" encoding="iso-8859-1"?>

<response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" command="run" transaction_id="2" status="break" reason="ok"><xdebug:message filename="dbgp://1" lineno="6"></xdebug:message></response>

2 | run > break/ok

2 | dbgp://1:6
(cmd) property_get -i 18 -d 0 -c 0 -n $this

<?xml version="1.0" encoding="iso-8859-1"?>

<response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" command="property_get" transaction_id="18"><property type="object" children="1" numchildren="1" page="0" pagesize="32"><name encoding="base64"><![CDATA[JHRoaXM=]]></name><fullname encoding="base64"><![CDATA[JHRoaXM=]]></fullname><classname encoding="base64"><![CDATA[Zm9vQGFub255bW91cwAvaG9tZS9kZXJpY2svZGV2L3BocC9kZXJpY2tyLXhkZWJ1Zy90ZXN0cy9kZWJ1Z2dlci9idWcwMjAyNS5pbmM6MTMkMA==]]></classname><property name="foo" fullname="$this->foo" facet="protected" type="string" size="3" encoding="base64"><![CDATA[YmFy]]></property></property></response>

18 | property_get

18 | object () {

18 |   string foo: bar

18 | }

cheers,
Derick

Hi Derick,

thank you for explaining what is missing in this case.

Maybe there is still something to do on the DAP adapter side - in both cases (enabled and disabled extended_properties).

What do you think about displaying a short tip from dbgpClient about this missing feature (I don't know how much PHP specific can be this tool)?

By the way, the URL from help command leads to non-existent page.

A short overview of commands is also available in the online
documentation at https://xdebug.org/docs/debugclient