Debugging possible Apache php_admin_value crash - Win32 crash trace possible?

> > Jani, > > Sorry I wasn't clear - I'm running 5.0.5 in development also. There is > something that happens with 5.0.5 + php_admin_value (or at least my > specific one) in production that I can't reproduce on another 5.0.5 > machine. I assume it has to do with me not being able to accurately > reproduce the load and page usage of real users. I can't speak at all > to if I do or don't see the same issue in 5.1 yet. > > Michael > > --- Jani Taskinen <sniper@iki.fi> wrote: > >> >> Then there is no problem. Next please. :) >> >> --Jani >> >> >> On Thu, 17 Nov 2005, Michael Sisolak wrote: >> >>> >>> Jani, >>> >>> Unfortunately I can't get this to reproduce in my development >>> environment and it's too early for me to switch to 5.1 in >> production. >>> >>> Michael >>> >>> --- Jani Taskinen <sniper@iki.fi> wrote: >>> >>>> >>>> Do you hit the same issue with using the latest PHP 5.1 >>>> snapshot? >>>> >>>> --Jani >>>> >>>> On Wed, 16 Nov 2005, Michael Sisolak wrote: >>>> >>>>> >>>>> I'm trying to debug an issue I'm seeing with PHP 5.0.5 and Apache >>>>> 2.0.55 (using apache2handler SAPI) running under Windows 2000 >>>> Server. >>>>> I need to set the mssql.max_procs setting to 300. If I change it >>>> in >>>>> php.ini everything works fine and the system is quite stable. To >>>> keep >>>>> all my config changes in one place, however, I wanted to use >>>>> php_admin_value in httpd.conf instead. As soon as I switched on >>>>> "php_admin_value mssql.max_procs 300", however, Apache2 started >>>>> resetting about every 10 minutes or so with errors like: >>>>> >>>>> [notice] Parent: child process exited with status 3221225477 -- >>>>> Restarting. >>>>> >>>>> I've tested several times and it routinely crashes when I use >>>>> php_admin_value and doesn't when I stick with just php.ini. Now >>>>> 3221225477 = 0xC0000005 = Access Violation so I assume there is >>>> some >>>>> kind of memory corruption happening, but I can't find a way to >>>> debug to >>>>> see what is going on here. Of course it only happens on my >>>> production >>>>> servers and I can't get it to reproduce anywhere else. >>>>> >>>>> Does anyone have suggestions about my next step to debug this? I >>>> need >>>>> to find out where the access violation is happening, but Apache >>>> eats >>>>> the error and restarts the process. Is there any magic that can >> be >>>>> used to tell Apache to let the error fall though so it can be >>>> caught by >>>>> Dr. Watson or something similar? Or a way to tell PHP to at >> least >>>>> record where the violation occurs on the crash? >>>>> >>>>> Michael Sisolak >>>>> msisolak@yahoo.com >>>>> >>>>> >>>>> >>>>> __________________________________ >>>>> Start your day with Yahoo! - Make it your home page! >>>>> http://www.yahoo.com/r/hs >>>>> >>>>> >>>> >>>> -- >>>> Give me your money at @ <http://pecl.php.net/wishlist.php/sniper> >>>> Donating money may make me happier and friendlier for a limited >>>> period! >>>> Death to all 4 letter abbreviations starting with P! >>>> >>> >>> >>> >>> >>> >>> __________________________________ >>> Yahoo! Mail - PC Magazine Editors' Choice 2005 >>> http://mail.yahoo.com >>> >> >> -- >> Give me your money at @ <http://pecl.php.net/wishlist.php/sniper> >> Donating money may make me happier and friendlier for a limited >> period! >> Death to all 4 letter abbreviations starting with P! >> > > > > > __________________________________ > Yahoo! FareChase: Search multiple travel sites in one click. > http://farechase.yahoo.com > >