ID: 37483
User updated by: jneill at gamedaytv dot com
Reported By: jneill at gamedaytv dot com
-Status: Feedback
+Status: Open
Bug Type: IIS related
Operating System: Windows 2003 SP 1
PHP Version: 5.1.4
New Comment:
I do not understand these instructions:
"When PHP crashes, click Cancel to debug the process. Now MSVC starts
up in Debug View. If you don't already see the call stack, go into the
View menu and choose Debug Windows → Call Stack."
When PHP crashes, we do not see a dialogue box with Cancel as an
option, and MSVC does not start up. All that happens is that we get an
error in the System Event Log that says something like:
---
A process serving application pool 'Site12' terminated unexpectedly.
The process id was '3392'. The process exit code was '0xc0000005'.
---
So how do I run the debugger?
Previous Comments:
------------------------------------------------------------------------
[2006-05-17 20:27:21] tony2001@php.net
Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php
for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php
for Win32
Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.
------------------------------------------------------------------------
[2006-05-17 20:05:34] jneill at gamedaytv dot com
Description:
------------
We have been successfully using PHP 5.1.2 for several months in our
server environment.
Only upgrading PHP to 5.1.4, with no other software upgrades, has
resulted in frequent w3svc crashes and subsequent application pool
terminations.
The system log includes such errors as:
---
A process serving application pool 'Site1' terminated unexpectedly. The
process id was '5796'. The process exit code was '0xc0000005'.
A process serving application pool 'Site2' terminated unexpectedly. The
process id was '5212'. The process exit code was '0xffffffff'.
A process serving application pool 'DefaultAppPool' terminated
unexpectedly. The process id was '5824'. The process exit code was
'0xc0000005'.
---
We have run the IIS Diagnostics Debug Diagnostics Tool on these
crashes, which has resulted in the following report for each crash:
---
Type of Analysis Performed Crash Analysis
Machine Name S76217
Operating System Windows Server 2003 Service Pack 1
Number Of Processors 2
Process ID 4736
Process Image c:\WINNT\system32\inetsrv\w3wp.exe
System Up-Time 0 day(s) 04:18:05
Process Up-Time 0 day(s) 00:31:08
Thread 16 - System ID 2612
Entry point msvcrt!_endthread+3b
Create time 5/16/2006 5:31:43 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
Function Arg 1 Arg 2 Arg 3 Source
<Unloaded_php5ts.dll>+265c80 02a28890 00000000 00000000
msvcrt!_endthread+ab 029e7580 00000000 00000000
kernel32!BaseThreadStart+34 77bcb35a 029e7580 00000000
In
w3wp__PID__4736__Date__05_16_2006__Time_05_31_45PM__95__Second_Chance_Exception_C0000005.dmp
an access violation exception (0xC0000005) occured on thread 16 when
another module attempted to call the following unloaded module:
php5ts.dll.
---
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=37483&edit=1