View Issue Details

IDProjectCategoryView StatusLast Update
0001747XdebugInstallationpublic2020-02-24 11:31
Reportertreytang Assigned Toderick  
PrioritynormalSeveritymajorReproducibilityalways
Status resolvedResolutionno change required 
Product Version2.9.2 
Summary0001747: XDebug Doesn't Get loaded into PHP
Description

Hey,

My php.ini file:

[xdebug]
zend_extension="/usr/lib/php/20170718/xdebug.so"
xdebug.remote_enable=1

As suggested by the /wizard page, but when I restart Apache and check phpinfo(); - xdebug isn't there ...

Steps To Reproduce

I followed the steps found at /wizard:

Summary

  • Xdebug installed: no
  • Server API: Apache 2.0 Handler
  • Windows: no
  • Zend Server: no
  • PHP Version: 7.2.27-6
  • Zend API nr: 320170718
  • PHP API nr: 20170718
  • Debug Build: no
  • Thread Safe Build: no
  • OPcache Loaded: no
  • Configuration File Path: /etc/php/7.2/apache2
  • Configuration File: /etc/php/7.2/apache2/php.ini
  • Extensions directory: /usr/lib/php/20170718

Instructions

  1. Download xdebug-2.9.2.tgz
  2. Install the pre-requisites for compiling PHP extensions.
    On your Ubuntu system, install them with: apt-get install php-dev autoconf automake
  3. Unpack the downloaded file with tar -xvzf xdebug-2.9.2.tgz
  4. Run: cd xdebug-2.9.2
  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.

  6. Run: ./configure
  7. Run: make
  8. Run: cp modules/xdebug.so /usr/lib/php/20170718
  9. Edit /etc/php/7.2/apache2/php.ini /etc/php/7.2/apache2/php.ini and add the line
    zend_extension = /usr/lib/php/20170718/xdebug.so
    10, Restart the webserver
TagsNo tags attached.
Attached Files
Operating SystemLinux Mint
PHP Version7.2.20-7.2.29

Activities

derick

2020-02-18 14:36

administrator   ~0005248

Does the file /usr/lib/php/20170718/xdebug.so exist?

treytang

2020-02-18 14:42

reporter   ~0005250

It does indeedy (see screeny)

derick

2020-02-18 14:53

administrator   ~0005251

Last edited: 2020-02-18 14:53

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

treytang

2020-02-18 15:07

reporter   ~0005252

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 :)

derick

2020-02-18 16:26

administrator   ~0005253

The wizard said the following:

  1. 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?

treytang

2020-02-18 16:32

reporter   ~0005254

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 :)

treytang

2020-02-18 16:37

reporter   ~0005255

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?

treytang

2020-02-18 16:46

reporter   ~0005256

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

treytang

2020-02-24 10:04

reporter   ~0005258

Hey,

any update on this?

Thanks,

derick

2020-02-24 10:12

administrator   ~0005259

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)

treytang

2020-02-24 11:10

reporter   ~0005260

Hey,

that did it thanks :)

derick

2020-02-24 11:31

administrator   ~0005261

This turned out not to be a bug (as I expected). Thanks for checking!

Issue History

Date Modified Username Field Change
2020-02-18 13:16 treytang New Issue
2020-02-18 14:36 derick Assigned To => derick
2020-02-18 14:36 derick Status new => feedback
2020-02-18 14:36 derick Note Added: 0005248
2020-02-18 14:42 treytang File Added: Screenshot from 2020-02-18 14-42-18.png
2020-02-18 14:42 treytang Note Added: 0005250
2020-02-18 14:42 treytang Status feedback => assigned
2020-02-18 14:53 derick Status assigned => feedback
2020-02-18 14:53 derick Note Added: 0005251
2020-02-18 14:53 derick Note Edited: 0005251
2020-02-18 15:07 treytang File Added: Screenshot from 2020-02-18 15-07-10.png
2020-02-18 15:07 treytang Note Added: 0005252
2020-02-18 15:07 treytang Status feedback => assigned
2020-02-18 16:26 derick Status assigned => feedback
2020-02-18 16:26 derick Note Added: 0005253
2020-02-18 16:32 treytang Note Added: 0005254
2020-02-18 16:32 treytang Status feedback => assigned
2020-02-18 16:37 treytang Note Added: 0005255
2020-02-18 16:46 treytang Note Added: 0005256
2020-02-24 10:04 treytang Note Added: 0005258
2020-02-24 10:12 derick Note Added: 0005259
2020-02-24 11:10 treytang Note Added: 0005260
2020-02-24 11:31 derick Status assigned => resolved
2020-02-24 11:31 derick Resolution open => no change required
2020-02-24 11:31 derick Note Added: 0005261