#31070 [NEW]: Possible integer overflow
| From: | dennis at inmarket dot lviv dot ua | Date: | Mon, 13 Dec 2004 14:25:33 +0000 |
| Subject: | #31070 [NEW]: Possible integer overflow | ||
| Groups: | php.bugs | ||
| Request: | Send a blank email to php-bugs+get-70148@lists.php.net to get a copy of this message | ||
From: dennis at inmarket dot lviv dot ua
Operating system: Linux
PHP version: 5.0.2
PHP Bug Type: Unknown/Other Function
Bug description: Possible integer overflow
Description:
------------
I believe this is related to bug 28945, but it is in No Feedback mode, and
I could not contact him to reopen it.
It OCASSIONALLY happens in my app (it is a large set of classes), and
writes to the error log even more amazing thing: here is the sample error
log entry:
[12-Nov-2004 15:50:52] PHP Fatal error: Possible integer overflow in
memory allocation (24 * 4294967295 + 0) in /**
* Returns a SQLDataBase implementation for database $name
*
* @param string $name database name
* @return SQLDataBase a SQLDataBase implementation for database
$name
*/ on line 11
The file that this scratch is ripped from is class definition, where no
memory allocation takes place (this is an abstract class)
Reproduce code:
---------------
It is not possible to reproduce this bug, it is a big set of classes
(about 170Kb source code), but it is caused by the engine I believe
(judging from how the error is reported)
Expected result:
----------------
At least the error log should be:
[12-Nov-2004 15:50:52] PHP Fatal error: Possible integer overflow in
memory allocation (24 * 4294967295 + 0) in <filename> on <line number>
Actual result:
--------------
12-Nov-2004 15:50:52] PHP Fatal error: Possible integer overflow in
memory allocation (24 * 4294967295 + 0) in /**
* Returns a SQLDataBase implementation for database $name
*
* @param string $name database name
* @return SQLDataBase a SQLDataBase implementation for database
$name
*/ on line 11
--
Edit bug report at http://bugs.php.net/?id=31070&edit=1
--
Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=31070&r=trysnapshot4
Try a CVS snapshot (php5.0): http://bugs.php.net/fix.php?id=31070&r=trysnapshot50
Try a CVS snapshot (php5.1): http://bugs.php.net/fix.php?id=31070&r=trysnapshot51
Fixed in CVS: http://bugs.php.net/fix.php?id=31070&r=fixedcvs
Fixed in release: http://bugs.php.net/fix.php?id=31070&r=alreadyfixed
Need backtrace: http://bugs.php.net/fix.php?id=31070&r=needtrace
Need Reproduce Script: http://bugs.php.net/fix.php?id=31070&r=needscript
Try newer version: http://bugs.php.net/fix.php?id=31070&r=oldversion
Not developer issue: http://bugs.php.net/fix.php?id=31070&r=support
Expected behavior: http://bugs.php.net/fix.php?id=31070&r=notwrong
Not enough info: http://bugs.php.net/fix.php?id=31070&r=notenoughinfo
Submitted twice: http://bugs.php.net/fix.php?id=31070&r=submittedtwice
register_globals: http://bugs.php.net/fix.php?id=31070&r=globals
PHP 3 support discontinued: http://bugs.php.net/fix.php?id=31070&r=php3
Daylight Savings: http://bugs.php.net/fix.php?id=31070&r=dst
IIS Stability: http://bugs.php.net/fix.php?id=31070&r=isapi
Install GNU Sed: http://bugs.php.net/fix.php?id=31070&r=gnused
Floating point limitations: http://bugs.php.net/fix.php?id=31070&r=float
MySQL Configuration Error: http://bugs.php.net/fix.php?id=31070&r=mysqlcfg