Segmentation fault using ionCube Loader v15.5.0, PHP 8.3+ and xDebug v3.5.0

[andp97]

Hi everyone,

we develop WHMCS modules and we are trying to find a reliable way to debug our own module code with Xdebug while running WHMCS with ionCube Loader enabled.

There is an open/closed Xdebug issue about crashes when Xdebug 3.3+ and ionCube Loader are loaded together:

https://bugs.xdebug.org/view.php?id=2244

Xdebug’s compatibility docs also state that Xdebug does not work together with ionCube or similar extensions that interact with PHP internals:

https://xdebug.org/docs/compat

Our current test setup is:

Xdebug: 3.5.1
PHP: 8.3 / 8.4
ionCube Loader: 15.5.0
Docker: php:8.3-fpm-bookworm / php:8.4-fpm-bookworm
Web server: httpd:alpine proxying to php-fpm

With this setup we get PHP segfaults. PHP 8.1 FPM does not seem to trigger the same issue for us.

We used PHP 8.1 since WHMCS v8.13, upgrading our stack to WHMCS 9.0 and PHP 8.3, we are unable to use xDebug.

We are not trying to debug WHMCS encoded core files. We only need WHMCS to run normally while debugging our own modules, hooks, and integration code.

Has anyone found a stable workflow for this?

Reaching the ionCube support we have this feedback:

Quote

Hi,
Thanks for creating a ticket.
This incompatibility is already known and there is no workaround for it.
The only way around this would be for the ionCube Loader to disable the internal Observer API (which Xdebug uses) which would mean that Xdebug would effectively be uninstalled. 
Apart from that we would have to completely re-engineer our encoding format since the problem stems from the byte code of encoded functions being in a different format from the "standard" byte code of functions in PHP after compilation.  
Kind regards,
--
ionCube Support

 

Any practical setup or workaround would be appreciated.

[andp97]

 @PapaKai  Maybe you encountered a similar issue?