I set up the debugger for a remote server as outlined in the instructions that were provided on this site. I was unable to get the debugger to work. The page just refreshes when you click the debug button the tool bar.

I ran the dbg-wizard to help set up debugging. It is telling me that my PHP extensions directory is: /usr/local/lib/php/extensions/no-debug-non-zts-20020429, however, the extensions_dir is set to /usr/local/php/extensions/ in my php.ini file.

Anyone know why my extensions directory would be set to /usr/local/lib/php/extensions/no-debug-non-zts-20020429 instead of the setting I provided in the php.ini file?

it may happen that you're editing wrong php.ini file. Please check phpinfo() to see where your php.ini file is.

That thought definitely crossed our minds. We checked and rechecked that to make sure. We even changed all the other php.ini to php.ini.bak just to make sure it wasn't reading the wrong one.

In all our searches we have been unable to find a solution to this so we have decided to trash the RedHat 9 box and intall Fedora 4 instead. Hopefully when it is all backup the debugger will work once again.

Did you by any chance forget to re-start httpd after you've made the changes to php.ini?

No, everything else on the server worked fine as before. PHP worked, it was serving web pages. We stopped the service, started it again. Restarted the server. Tried moving the .so files the extensions folder that it thought it was supposed to use. None of those worked.

The only thing I can possibly think that happened is that when we added apache2 as an alternate server on port 8080 it somehow changed the settings. I just don't know what settings it changed or how to change it back so that it would use the appropriate extensions directory.

I appreciate your help.

Does phpinfo() show path php.ini at all? This path is what php sees and where php loads the configuration from.
Also check that the path is correct. Just copy-paste and run ls -la against it in the console.

If your php does not see its php.ini, it won't load the modules specified there, including the debugger.

Was there any resolution to this issue. I'm having similar issue installing DBG into my Apache/PHP environment.
When I add the line: extension=dbg-php-5.1.so and restart apache, the website mywebserver hangs.
When it is commented out, and apache restarted, the web site home page comes up. I placed the dbg-wizard.php
link on the site as well as placing phpinfo() on homepage. Just getting a new Network Solutions VPS hosting account
running, so I'm all about getting the debugger working for PhpEd 5.6 development. here's what the wizard shows me:


PHP Version: 5.1.6
Web Server: Apache/2.2.3 (Fedora)
Server Name: mywebserver
Platform: Linux-glibc-2.5/x86_64
Your Client IP Address: 75.145.158.206
Your Server IP Address: 69.161.223.223
Port: 80
Your Web Server and PhpED are on different machines
Path to website files: /var/www/vhosts/ADOREU.ORG/httpdocs/
Document Root is: /var/www/vhosts/ADOREU.ORG/httpdocs/
Your PHP.INI file is: /etc/php.ini
PHP extensions directory is: /usr/lib64/php/modules
DBG (PHP DEBUGGER) is not installed


I'm thinking that there's a conflict between the PHP 5.1 compile time switches and the DBG extension
I issued a "php -m" command. Here's what it shows me...


[PHP Modules]
bz2
calendar
ctype
curl
date
dom
exif
ftp
gd
gettext
gmp
hash
iconv
imap
ionCube Loader
libxml
mbstring
mime_magic
mysql
mysqli
openssl
pcntl
pcre
PDO
pdo_mysql
pdo_sqlite
posix
pspell
Reflection
session
shmop
SimpleXML
sockets
SPL
standard
sysvmsg
sysvsem
sysvshm
tokenizer
wddx
xml
xmlreader
xmlwriter
xsl
zlib

[Zend Modules]
the ionCube PHP Loader




Any help in getting this issue resolved would be greatly appreciated.

Joe

Does it mean that DBG causes the hang?
Not at all. You have plenty of the other extensions that may look for DBG and work differently if they see that you're trying to load this module.
For example, ioncube loaders demonstrates this nasty behaviour. They promised to remove/fix the problem long time ago, but they still havn't.

In all our searches we have been unable to find a solution to this so we have decided to trash the RedHat 9 box and intall Fedora 4 instead. Hopefully when it is all backup the debugger will work once again.

That is pretty much what we did. I was not able to get any of it to work so we had to trash it and start over. Running Fedora 10 and back installed, from source, php 4.4.9, mysql 4.1.22, and apache 2