Bug #53333 [Fbk]: Random crash

Edit report at http://bugs.php.net/bug.php?id=53333&edit=1 ID: 53333 Updated by: andrey@php.net Reported by: pajoye@php.net Summary: Random crash Status: Feedback Type: Bug Package: MySQLi related Operating System: * PHP Version: 5.3.3 Assigned To: mysql Block user comment: N Private report: N New Comment: Hi, I recently fixed the argument parser for the debug log for Windows, because ":" is a separator in the string. Also only since few weeks the trace log is available on Windows. You need a pretty fresh build sources. Also you need a _debug_ build, because the trace functionality is not compiled in in release builds. And please try using / instead of \, if that helps. Previous Comments: ------------------------------------------------------------------------ [2010-12-01 10:49:22] kriscraig@php.net Oh and also, could you tell me when this debug is supposed to output the file? I.e. does it output debug info whenever MySQL is invoked, or only when there's a crash? ------------------------------------------------------------------------ [2010-12-01 10:39:51] kriscraig@php.net Hi Ulf, I've been running the tests for Pierre and am also the one who first discovered this bug. He asked me to connect with you here because I've been unable to get the debug directive you mentioned to output. Specifically, I'm running the PHP 5.3.4RC1 ZTS Pierre released, VC9 compile, on Apache 2.2 under one of our Windows 2008 R2 hosts with Windbg attached to the process. In php.ini, I added the following line to the MYSQLND section: mysqlnd.debug="d:t:O,C:\temp\mysqlnd_debug.log" The setting does show up in PHPInfo(). Specifically: mysqlnd mysqlnd enabled Version mysqlnd 5.0.7-dev - 091210 - $Revision: 304625 $ Compression supported SSL not supported Command buffer size 4096 Read buffer size 32768 Read timeout 31536000 Collecting statistics Yes Collecting memory statistics Yes Tracing d:t:O,C:\temp\mysqlnd_debug.log However, the mysqlnd_debug.log file is never created. I'm not sure under what conditions it's supposed to output, but in this test I was hitting both MediaWiki and WordPress until the crash occured, and at no point was the file created. The directory has full perms (including write) granted to all users. I could theoretically use procmon to see if it's attempting to write the file, but since we're dealing with a bug that takes about an hour to repro, that wouldn't be my first choice. Have you had a chance yet to test this new debug feature? Do you know if there are any other settings/etc that need to be enabled in order for this to work? Please let me know and I'll give it another go. Thanks! --Kris ------------------------------------------------------------------------ [2010-11-30 12:26:20] pajoye@php.net I will ask to enable it and run again the tests. Thanks :) ------------------------------------------------------------------------ [2010-11-30 12:24:45] uw@php.net Hi Pierre, can you provide a mysqlnd debug log, do you have access to the php.ini? In 5.3.4 mysqlnd learned to write proper debug logs on Windows. Try running PHP with mysqlnd.debug="d:t:O,C:\mysqlnd_debug.log". You need 5.3.4. 5.3.3 won't do it. Thanks, Ulf ------------------------------------------------------------------------ [2010-11-29 14:12:14] pajoye@php.net Yes, it happens as well with current SVN (5.3.4RC1 too). ------------------------------------------------------------------------ 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/bug.php?id=53333 -- Edit this bug report at http://bugs.php.net/bug.php?id=53333&edit=1