|
|
Does the file /usr/lib/php/20170718/xdebug.so exist? |
|
|
It does indeedy (see screeny)
Screenshot from 2020-02-18 14-42-18.png (94,187 bytes) |
|
|
If you run the following on the command line, do you get warnings or errors? And what is the output?php -ddisplay_startup_errors=1 -c /etc/php/7.2/apache2/php.ini -v |
|
|
Screenshot from 2020-02-18 15-07-10.png (47,365 bytes) |
|
|
Hey, attached is output, however, I altered the command as I have various versions of PHP on my machine and it defaults to 7.4 in cli :) |
|
|
The wizard said the following:
5. Run: phpize (See the FAQ if you don't have phpize).
As part of its output it should show:
Configuring for:
...
Zend Module Api No: 20170718
Zend Extension Api No: 320170718
If it does not, you are using the wrong phpize. Please follow this FAQ entry and skip the next step.
And the start-up error that you are getting indicates that you have compiled Xdebug against the wrong PHP version (7.4, I believe). If you verify the numbers for that step, do they match with what the wizard said they should be? |
|
|
ahh I have a phpize7.2 as well as a phpize - which I guess defaults to CLI version (7.4), lemme re-build using the correct phpize :) |
|
|
I think the previous installation is conflicting my amendments, is there a sure-fire way of removing everything xdebug? Guessing apt purge won't work here? |
|
|
Found a way (just manual removing) - but still same issue after using phpize7.2 (same error shown when using that php -display_startup_errors command |
|
|
Hey, any update on this? Thanks, |
|
|
Using phpize7.2 is only part of the store in this case. When you then run ./configure, you will need to add --with-php-config=/usr/local/php/7.2dev/bin/php-config (but fix the path, as yours is different from mine) |
|
|
Hey, that did it thanks :) |
|
|
This turned out not to be a bug (as I expected). Thanks for checking! |
- Anonymous
