ID:               44645
 Comment by:       hiperjp 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 had the same problem too, I am using PHP 5.2.6 on Windows XP SP3 and
las mysql 5.1.22 and Apache 2.2.10 (similar to friend above), with MySQL
5.0.x I am not have this problem.


Previous Comments:
------------------------------------------------------------------------

[2008-11-26 11:00:58] ali at bleurider dot com

I had the same problem too, I am using PHP5.2.6 on Windows XP SP2,
MySql 5.1.22 and Apache 2.2.10. 
I am a J2EE Developer originally, but wanted to toy around with PHP, it
was too frustrating but finally I changed the said libmySQL.dll to
libmySQL.dll_ in MySQL, which is a ridiculous remedy but works.
PHP folks, you just can't get away by saying there is no trace report,
you want to be on top, gotta pay the price and move you butt and fix
such bugs.
FYI, I had to help my cuz customizing his xcart installation.
such a waste of time and money anyway.

------------------------------------------------------------------------

[2008-11-18 01:00:02] php-bugs at lists dot php dot net

No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

------------------------------------------------------------------------

[2008-11-14 22:38:08] dhulme at gmail dot com

Update:

5.2.7RC4 did not help, in fact it crashed even more quickly.  However,
I don't know for sure what caused it as it was reporting "out of memory"
errors before it crashed.  5.2.6 did not have this problem, so I don't
know if 5.2.7 really has the same problem or a new one.

-Dan

------------------------------------------------------------------------

[2008-11-14 19:38:21] dhulme at gmail dot com

I have seen several reports like this, all of which are unresolved,
dating back as far as 2005.  Someone asks for a backtrace, someone posts
one, and then nothing happens.  It's like you think the backtrace will
help you solve the bug, but when it doesn't, you suddenly become
silent.

I am running into the same problem as this forum.  I cannot post a
backtrace because this is a production server and I am trying to limit
changes on this server.  However, my info is as follows:

Windows Server 2003 R2 SP2
Apache 2.2.10
PHP 5.2.6

-----------------------------------------------------------------
Faulting application httpd.exe, version 2.2.10.0, faulting module
php5ts.dll, version 5.2.6.6, fault address 0x000ad094.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-----------------------------------------------------------------

I was error free for a couple months after remove "php_gd2.dll" from
the extensions I was using (I removed all I thought I wasn't using). 
Then I found out I had been using it in one obscure script, so I added
it back.  The same day I got another one of these crashes.  So I suspect
it has to do with that.

Hopefully this information helps someone more than asking for a
backtrace and then never giving any more help.

Currently I upgraded to the RC4 build of 5.2.7 to see if that helps.  I
will check back in a few days if it solves the problem.

Good Luck!

Dan

------------------------------------------------------------------------

[2008-11-10 12:51:47] [EMAIL PROTECTED]

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.

Unless you provide a backtrace there is little chance for us to even
try to solve the crash.

I would also recommend to do not use any non core extension while
testing (blenc or any other zend optimizer or debugger).

See my previous comment to know how to generate a backtrace.

------------------------------------------------------------------------

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

Reply via email to