Honest, your best bet to start debugging this is to place PHP5+PGPGACL into a stable environment. If it doesn't reproduce there, introduce a semi-stable environment (i.e. any recent Apache2 release). Again if it doesn't reproduce there, move to your extremely volitile setup you've got currently and hope for a chance to attach your debugger to it.
Personally, I'd start with the PHP5 cgi/cli and see if it happens there. Easiest way to reproduce and debug the code.
On Jun 16, 2004, at 5:56 PM, OpenMacNews wrote:
-- On Wednesday, June 16, 2004 2:49 PM -0700 Dan Kalowsky <[EMAIL PROTECTED]> wrote:
A good start would be to move away from a completely developer environment like you're using. I'd suggest either working with PHP5 or Apache2-dev, but not both at the same time. That should help you narrow things down a bit more. In reality, I'd narrow to Apache1 as well if you're trying to debug some bit of code in PHP.
fair point, but its exactly this "manybody" developer environment i'm trying to debug. i've had do other probs (so far ...) w/ the setup i'm using.
if seems that something in the phpgacl 'stuff' is causing php5+apache to choke ... the question -- for me -- is HOW to track down WHAT the issue is.
that said, THIS problem is reproducible with apache 2.0.49 as well ...
richard
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
