Re: [PHP-WIN] Re: CLI Crash Bug

2013-08-16 Thread Jan Ehrhardt
Eric Stenson in php.windows (Thu, 25 Jul 2013 18:35:25 +): >I've filed bug https://bugs.php.net/bug.php?id=65338 to track this >issue. The root cause of the AV is when more than one module hooks the >interned strings, a "wrong" value will be left in >CG(interned_strings_start), which the Zend

Re: [PHP-WIN] Re: CLI Crash Bug

2013-07-30 Thread Jan Ehrhardt
Keith Davis in php.windows (Tue, 30 Jul 2013 15:57:05 -0500): >But I thought from the previous fix, what was updated was php5.dll. So, >to be clear, I want to use a base (revert my php5.dll file to base) >5.5.1 build with the new php_wincache.dll and php_opcache.dll files? Yes. Dmitry took another

RE: [PHP-WIN] Re: CLI Crash Bug

2013-07-30 Thread Keith Davis
For clarity, I'm testing the whole 5.5.2-dev build. Seems to work fine. Keith Davis (214) 906-5183 From: Keith Davis [mailto:keithda...@pridedallas.com] Sent: Tuesday, July 30, 2013 3:57 PM To: php-windows@lists.php.net Subject: RE: [PHP-WIN] Re: CLI Crash Bug But I thought from the pre

RE: [PHP-WIN] Re: CLI Crash Bug

2013-07-30 Thread Keith Davis
...@ehrhardt.nl] Sent: Tuesday, July 30, 2013 11:25 AM To: php-windows@lists.php.net Subject: Re: [PHP-WIN] Re: CLI Crash Bug Jan Ehrhardt in php.windows (Tue, 30 Jul 2013 18:15:50 +0200): >Keith Davis in php.windows (Fri, 26 Jul 2013 16:24:26 -0500): >>Ok, I copied both php

Re: [PHP-WIN] Re: CLI Crash Bug

2013-07-30 Thread Jan Ehrhardt
Jan Ehrhardt in php.windows (Tue, 30 Jul 2013 18:15:50 +0200): >Keith Davis in php.windows (Fri, 26 Jul 2013 16:24:26 -0500): >>Ok, I copied both php5.dll and php_wincache.dll from the ones you >>compiled, Jan, with Eric's patch and it works! > >New compilation without Eric's patch, but with Dmitry

Re: [PHP-WIN] Re: CLI Crash Bug

2013-07-30 Thread Jan Ehrhardt
Keith Davis in php.windows (Fri, 26 Jul 2013 16:24:26 -0500): >Ok, I copied both php5.dll and php_wincache.dll from the ones you >compiled, Jan, with Eric's patch and it works! New compilation without Eric's patch, but with Dmitry's patch of today: https://dl.dropboxusercontent.com/u/8954372/php-5

Re: [PHP-WIN] Re: CLI Crash Bug

2013-07-26 Thread Jan Ehrhardt
Eric Stenson in php.windows (Thu, 25 Jul 2013 18:35:25 +): >I've filed bug https://bugs.php.net/bug.php?id=65338 to track this >issue. The root cause of the AV is when more than one module hooks the >interned strings, a "wrong" value will be left in >CG(interned_strings_start), which the Zend

RE: [PHP-WIN] Re: CLI Crash Bug

2013-07-26 Thread Keith Davis
Ok, I copied both php5.dll and php_wincache.dll from the ones you compiled, Jan, with Eric's patch and it works! https://dl.dropboxusercontent.com/u/8954372/php-5.5.1-nts-Win32-VC11-x86.zip Updated both bug reports confirming this as well. This message (including any attachments) may contain

Re: [PHP-WIN] Re: CLI Crash Bug

2013-07-26 Thread Jan Ehrhardt
Keith Davis in php.windows (Fri, 26 Jul 2013 13:52:53 -0500): >Jan, this version does not work (crashed.) Crashed at startup or on closing? What is the date of php_wincache.dll? Should be something like 2013-07-26 17:49. Filesize: 131584. Maybe dropbox did not synchronize yet... >I'm showing Fil

RE: [PHP-WIN] Re: CLI Crash Bug

2013-07-26 Thread Keith Davis
Jan, this version does not work (crashed.) I'm showing File Version of 1.3.5.0. Keith Davis - (214) 906-5183 -Original Message- From: Jan Ehrhardt [mailto:php...@ehrhardt.nl] Sent: Friday, July 26, 2013 12:25 PM To: php-windows@lists.php.net Subject: Re: [PHP-WIN] Re: CLI Cras

Re: [PHP-WIN] Re: CLI Crash Bug

2013-07-26 Thread Jan Ehrhardt
Eric Stenson in php.windows (Thu, 25 Jul 2013 18:35:25 +): >I've filed bug https://bugs.php.net/bug.php?id=65338 to track this >issue. The root cause of the AV is when more than one module hooks the >interned strings, a "wrong" value will be left in >CG(interned_strings_start), which the Zend

RE: [PHP-WIN] Re: CLI Crash Bug

2013-07-25 Thread Eric Stenson
Keith-- I haven't figured out how to resolve bugs as duplicate on the bugs.php.net site. Thx! --E. From: Keith Davis [mailto:keithda...@pridedallas.com] Sent: Thursday, July 25, 2013 12:04 PM To: php-windows@lists.php.net Subject: RE: [PHP-WIN] Re: CLI Crash Bug Thanks Eric.

RE: [PHP-WIN] Re: CLI Crash Bug

2013-07-25 Thread Keith Davis
Thanks Eric. I had already created a bug report this issue here: https://bugs.php.net/bug.php?id=65247&thanks=3 Yours is obviously a better report of the issue, and so I've referenced yours in mine. Is there a way for bugs to marked duplicate in this bug report system? Keith Davis - (214) 906-

RE: [PHP-WIN] Re: CLI Crash Bug

2013-07-23 Thread Keith Davis
: Jan Ehrhardt [mailto:php...@ehrhardt.nl] Sent: Tuesday, July 23, 2013 12:24 PM To: php-windows@lists.php.net Subject: Re: [PHP-WIN] Re: CLI Crash Bug Keith Davis in php.windows (Tue, 23 Jul 2013 06:43:06 -0500): >It's only with: >wincache.enablecli=1 & opcache.enable_cli=1 OK. And those

Re: [PHP-WIN] Re: CLI Crash Bug

2013-07-23 Thread Jan Ehrhardt
Keith Davis in php.windows (Tue, 23 Jul 2013 06:43:06 -0500): >It's only with: >wincache.enablecli=1 & opcache.enable_cli=1 OK. And those two do not go along when php is running from th ecommandline. They produce errors while closing the script. There is a nasty workaround: leave PHP before the e

RE: [PHP-WIN] Re: CLI Crash Bug

2013-07-23 Thread Keith Davis
--Original Message- From: Jan Ehrhardt [mailto:php...@ehrhardt.nl] Sent: Tuesday, July 23, 2013 4:01 AM To: php-windows@lists.php.net Subject: Re: [PHP-WIN] Re: CLI Crash Bug Keith Davis in php.windows (Mon, 22 Jul 2013 12:49:59 -0500): >A, geez. It looks like it's caused by Wincache.

Re: [PHP-WIN] Re: CLI Crash Bug

2013-07-23 Thread Jan Ehrhardt
Keith Davis in php.windows (Mon, 22 Jul 2013 12:49:59 -0500): >A, geez. It looks like it's caused by Wincache. I disable and >enable that extension and the crashing stops and starts. > >However, again, I've tested Wincache thoroughly with Opcache in >IIS and have no issues. It's only on the com

RE: [PHP-WIN] Re: CLI Crash Bug

2013-07-22 Thread Keith Davis
- (214) 906-5183 -Original Message- From: Jan Ehrhardt [mailto:php...@ehrhardt.nl] Sent: Monday, July 22, 2013 6:10 PM To: php-windows@lists.php.net Subject: Re: [PHP-WIN] Re: CLI Crash Bug Keith Davis in php.windows (Mon, 22 Jul 2013 12:49:59 -0500): >A, geez. It looks like it's c

Re: [PHP-WIN] Re: CLI Crash Bug

2013-07-22 Thread Jan Ehrhardt
Keith Davis in php.windows (Mon, 22 Jul 2013 12:49:59 -0500): >A, geez. It looks like it's caused by Wincache. I disable and enable >that extension and the crashing stops and starts. > >However, again, I've tested Wincache thoroughly with Opcache in IIS and >have no issues. It's only on the com

RE: [PHP-WIN] Re: CLI Crash Bug

2013-07-22 Thread Keith Davis
p...@ehrhardt.nl] Sent: Monday, July 22, 2013 11:04 AM To: php-windows@lists.php.net Subject: Re: [PHP-WIN] Re: CLI Crash Bug Keith Davis in php.windows (Mon, 22 Jul 2013 10:36:32 -0500): >"Maybe the developers of OPcache can do something with this >information, although it is deep insid

RE: [PHP-WIN] Re: CLI Crash Bug

2013-07-22 Thread Keith Davis
) 906-5183 -Original Message- From: Jan Ehrhardt [mailto:php...@ehrhardt.nl] Sent: Monday, July 22, 2013 11:04 AM To: php-windows@lists.php.net Subject: Re: [PHP-WIN] Re: CLI Crash Bug Keith Davis in php.windows (Mon, 22 Jul 2013 10:36:32 -0500): >"Maybe the developers of OPcache can

Re: [PHP-WIN] Re: CLI Crash Bug

2013-07-22 Thread Jan Ehrhardt
Keith Davis in php.windows (Mon, 22 Jul 2013 10:36:32 -0500): >"Maybe the developers of OPcache can do something with this information, >although it is deep inside Windows. Is it a Windows Server? Which >edition? 2008 R2 or higher?" > >How do I contact them? https://github.com/zendtech/ZendOptimiz

RE: [PHP-WIN] Re: CLI Crash Bug

2013-07-22 Thread Keith Davis
Subject: Re: [PHP-WIN] Re: CLI Crash Bug Keith Davis in php.windows (Mon, 22 Jul 2013 08:04:44 -0500): >Program received signal SIGTRAP, Trace/breakpoint trap. >0x7756e696 in ntdll!KiRaiseUserExceptionDispatcher () > from C:\Windows\system32\ntdll.dll Your bug report was talking about C

RE: [PHP-WIN] Re: CLI Crash Bug

2013-07-22 Thread Keith Davis
ine (which is what we use in production), if that would help. Keith Davis - (214) 906-5183 -Original Message- From: Jan Ehrhardt [mailto:php...@ehrhardt.nl] Sent: Monday, July 22, 2013 8:45 AM To: php-windows@lists.php.net Subject: Re: [PHP-WIN] Re: CLI Crash Bug Keith Davis in php.wi

Re: [PHP-WIN] Re: CLI Crash Bug

2013-07-22 Thread Jan Ehrhardt
Keith Davis in php.windows (Mon, 22 Jul 2013 08:04:44 -0500): >Program received signal SIGTRAP, Trace/breakpoint trap. >0x7756e696 in ntdll!KiRaiseUserExceptionDispatcher () > from C:\Windows\system32\ntdll.dll Your bug report was talking about C:\Windows\SysWOW64\ntdll.dll https://bugs.php.net/

Re: [PHP-WIN] Re: CLI Crash Bug

2013-07-22 Thread Jan Ehrhardt
Keith Davis in php.windows (Mon, 22 Jul 2013 08:04:44 -0500): >Seems to be the same problem with this method, no debugging symbols found. >I've added the debug pack to my c:\PHP directory (with the extension >.pdb files in \ext.) I had the same problem. I am not sure if the GNU debugger looks at

RE: [PHP-WIN] Re: CLI Crash Bug

2013-07-22 Thread Keith Davis
Seems to be the same problem with this method, no debugging symbols found. I've added the debug pack to my c:\PHP directory (with the extension .pdb files in \ext.) C:\temp>gdb32.exe php.exe GNU gdb (GDB) 7.5.1 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 o

RE: [PHP-WIN] Re: CLI Crash Bug

2013-07-20 Thread Keith Davis
Good to know. Keith Davis - (214) 906-5183 -Original Message- From: Jan Ehrhardt [mailto:php...@ehrhardt.nl] Sent: Saturday, July 20, 2013 8:50 AM To: php-windows@lists.php.net Subject: [PHP-WIN] Re: CLI Crash Bug Keith Davis in php.windows (Sat, 20 Jul 2013 07:14:39 -0500): >We are try

RE: [PHP-WIN] Re: CLI Crash Bug

2013-07-20 Thread Keith Davis
The problem with using the x64 version just for command line is we are running PHPUnit and composer and we need the build to be the same as production - which is running IIS. We are planning on doing some straight command line stuff on a production box as well, and this x64 info is good to know