Im running php 5.1.2 (mostly CLI) on FreeBSD 6. I compiled Xdebug 2 and
PHPized it. It was working great until I turned on the trace file feature.
It would spit out 6 gigs of trace data in 1 hour and would constantly lock
my system up from the file system being full. I did what any logical person
would do and turned off the trace functionality and restarted Apache/PHP.
This did not stop the files from being traced. I started to panic a bit and
so I turned off EVERY xdebug feature in php.ini, including the
zend_extension_debug line (Im using php with debug on). I started the entire
server and it still didn't take. Finally I decided to stop apache, recompile
PHP from port, and start it up again. Xdebug was STILL writing trace files.
I finally got a duct tape and coat hanger solution into place by renaming
the shared object file it's looking for, but now it complains that it can't
find it any time a script starts up. Normally this wouldn't be that big of a
deal but I have some PHP cron jobs running every minute so I am getting
bombarded with 'cannot find xdebug.so' messages. What the heck do I need to
do to stop PHP from thinking it still has xdebug? Thanks in advance.
Received on Wed Jan 25 2006 - 17:17:49 GMT
This archive was generated by hypermail 2.2.0 : Mon Jun 25 2018 - 06:00:04 BST