#44645 [Com]: php5ts.dll Crash (x86_64 base machines)
| From: | collins dot ethans at gmail dot com | Date: | Sun, 17 Aug 2008 08:47:28 +0000 |
| Subject: | #44645 [Com]: php5ts.dll Crash (x86_64 base machines) | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-128139@lists.php.net to get a copy of this message | ||
ID: 44645
Comment by: collins dot ethans at gmail dot com
Reported By: gary dot wilson at coull dot biz
Status: No Feedback
Bug Type: Reproducible crash
Operating System: Windows Server 2003
PHP Version: 5.2.5
New Comment:
I installed PHP 5.2.6 yesterday on x86 64bit machine running WinXP SP2
(32 bit), using php-5.2.6-win32-installer.msi. I could reproduce the
problem easily. I used a cmd prompt and ran 'php -v'. It immediately
pops up a problem window saying, "CLI has encountered a problem and
needs to close. We are sorry for the inconvenience." The detailed
report says: ModName: php5ts.dll, ModVer: 5.2.6.6, Offset: 0009c51d.
However, with the crash, it also prints the version on the shell and
does it 6 times, poping up the error window 6 times !
Is there a solution to this problem ? I wanted to learn PHP (being a
pythoner) and this is not allowing me to move forward. Any
help/workaround for timebeing is appreciated.
Previous Comments:
------------------------------------------------------------------------
[2008-08-06 15:10:24] sylvaint at sylvaint dot ca
This bug is not strictly unique to X64 based machines.
The Same bug appeared while using an X32 based machine and the same
solution worked.
Thanks
------------------------------------------------------------------------
[2008-08-02 22:05:01] lotusxxl at gmail dot com
Event viewer shows:
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 02/08/2008
Time: 20:17:41
User: N/A
Computer: SERVERX64
Description:
Faulting application httpd.exe, version 2.2.9.0, faulting module
php5ts.dll, version 5.2.5.5, fault address 0x000000000000e8e4.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 68 74 74 ure htt
0018: 70 64 2e 65 78 65 20 32 pd.exe 2
0020: 2e 32 2e 39 2e 30 20 69 .2.9.0 i
0028: 6e 20 70 68 70 35 74 73 n php5ts
0030: 2e 64 6c 6c 20 35 2e 32 .dll 5.2
0038: 2e 35 2e 35 20 61 74 20 .5.5 at
0040: 6f 66 66 73 65 74 20 30 offset 0
0048: 30 30 30 30 30 30 30 30 00000000
0050: 30 30 30 65 38 65 34 000e8e4
------------------------------------------------------------------------
[2008-08-02 19:53:36] pajoye@php.net
"I fix this bug renaming the libmysql.dll in C:\Program
Files\MySQL\MySQL
Server 5.1\bin to libmysql.dll_
Now php uses libmysql.dll in c:\php directory and phpinfo shows Client
Api version 5.0.19. Before showed 5.1.25rc"
Ah that is definitively a good thing to do, using 5.1 DLLs with PHP
binaries is wrong.
About the backtrace, it seems that you are missing the debug pack, I
can't see any symbols ( Error WARNING - DebugDiag was not able to
locate debug symbols for php5ts.dll, so the information below may be
incomplete.).
------------------------------------------------------------------------
[2008-08-02 18:50:58] lotusxxl at gmailc dot om
I fix this bug renaming the libmysql.dll in C:\Program
Files\MySQL\MySQL Server 5.1\bin to libmysql.dll_
Now php uses libmysql.dll in c:\php directory and phpinfo shows Client
Api version 5.0.19
Before showed 5.1.25rc
It works fine with Apache 2.2.9 x64 and PHP 5.2.5 x64 version in
Windows 2003 Server Standard x64
------------------------------------------------------------------------
[2008-07-28 12:08:40] neil dot smith at coull dot com
[5 Jul 12:38pm UTC] pajoye@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"
[3 Jun 4:11pm UTC] neil dot smith at coull dot com
Debug backtrace was already provided on 3rd June as required - was that
not the information you were requesting ?
Please consider reactivating this bug and reviewing the backtrace
provided. We can retry the repro case and provide additional information
if needed, but that appears to be what was requested.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/44645
--
Edit this bug report at http://bugs.php.net/?id=44645&edit=1