apd-0.4p2 barely functioning
| From: | Roman Neuhauser | Date: | Mon, 22 Sep 2003 05:25:01 +0000 |
| Subject: | apd-0.4p2 barely functioning | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-21873@lists.php.net to get a copy of this message | ||
Hi there,
I've installed apd-0.4p2 on a FreeBSD 4.8-STALE box with apache-1.3.28
and php-4.3.3. It looks like apd barely does anything, and that anything
is useless because unreliable. I can't believe this is a problem with
apd, so I'm not filing a PR, but rather asking here.
* the constants named MUMBLE_TRACE consistently across the documentation
(the online manual, and the README) are actually APD_MUMBLE_TRACE.
* after starting apache, apd_set_session_trace() only outputs
APD - Advanced PHP Debugger Trace File
---------------------------------------------------------------------------
Process Pid (85674)
Trace Begun at Mon Sep 22 07:09:51 2003
---------------------------------------------------------------------------
( 0.000000): apd_set_session_trace called at /usr/var/db/www/servis.fp/PMSystem/global.php:7
( 0.790119): RSHUTDOWN called - end of trace
---------------------------------------------------------------------------
Process Pid (85674)
% time usecs usecs/call calls function
----- ----- ---------- ----- --------
---------------------------------------------------------------------------
Trace Ended at Mon Sep 22 07:09:52 2003
---------------------------------------------------------------------------
until I fuck with the apd_* functin calls long enough, and then it
gives a listing of all functions/methods called, but all are reported
with zero times, and just one call!
apd_set_pprof_trace() sometimes "works", sometimes reports
"Fatal error: apd_set_pprof_trace() failed to open 111/pprof.85679 for
tracing in ..."
All in all, looks like there's some corruption going on.
Where should I look?
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html