ID: 36722
Comment by: johan at solace dot miun dot se
Reported By: michael dot virnstein at brodos dot de
Status: No Feedback
Bug Type: Unknown/Other Function
Operating System: SuSE Linux 9.0
PHP Version: 4.4.2
New Comment:
A few weeks back, my websites suddenly started throwing random
occurences of this message in different php-files...
Fatal error: Possible integer overflow in memory allocation (5 * 1 +
42) in /usr/local/webroot/www.imagine3d.org/html/mainfile.php on line
54
It happens in different php applications, like xoops and phpMyAdmin and
even during the install of never version of php during its pear install
part which is php.
I upgraded apache to 2.0.61 and php to 4.4.7 with no change.
fault seems to incure in different string and preg calls in the various
applications but I havent been able to make a reproducable small and
simple code example.
The fault comes up randomly, but quite often... sometimes it also
just dies... no error...
System is a 12CPU Sun Enterprise 4500 with 12GB Ram,no hardware faults
visible in logs, running Solaris 9.
Previous Comments:
------------------------------------------------------------------------
[2007-05-06 02:58:11] Alexander at Kriegisch dot name
PHP Fatal error: Possible integer overflow in memory allocation (8 * 4
+ 0) in Unknown on line 0
This was reported by a user trying to start a statically compiled PHP
5.2.1 (sapi/cgi binary) from an Apache 1.3.37. I cannot reproduce it on
my router box, because it runs a 2.6 kernel, I just compiled the version
for him (GCC 4.1.0, binutils 2.16.91.0.6, uClibc 0.9.26,
crosstool-0.42).
Just wanted to add this to make clear that other users on other
platforms and with other PHP versions have this problem, too. I cannot
tell if the cause is the same, though.
------------------------------------------------------------------------
[2006-03-23 01:00:05] 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".
------------------------------------------------------------------------
[2006-03-15 13:48:20] [EMAIL PROTECTED]
Yes, and this information is a reproduce case.
------------------------------------------------------------------------
[2006-03-14 12:27:57] michael dot virnstein at brodos dot de
Is there a way i can provide mor information to you, by setting e.g. a
php directive to get more information when such an error occures
------------------------------------------------------------------------
[2006-03-13 19:25:53] [EMAIL PROTECTED]
Well, I'm afraid you're on your own with this problem, as apparently
nobody except you is able reproduce it and it looks like there is no
reproduce code for the issue.
------------------------------------------------------------------------
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/36722
--
Edit this bug report at http://bugs.php.net/?id=36722&edit=1
