#32422 [NoF->Bgs]: Access Violation on calling PEAR Date::before
| From: | pajoye@php.net | Date: | Mon, 26 Jun 2006 10:38:24 +0000 |
| Subject: | #32422 [NoF->Bgs]: Access Violation on calling PEAR Date::before | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-98772@lists.php.net to get a copy of this message | ||
ID: 32422
Updated by: pajoye@php.net
Reported By: rob at wildlime dot com
-Status: No Feedback
+Status: Bogus
Bug Type: Reproducible crash
Operating System: Windows XP SP2
PHP Version: 4.3.10
Assigned To: pierre
New Comment:
Sorry, but your problem does not imply a bug in PHP itself. For a
list of more appropriate places to ask for help using PHP, please
visit http://www.php.net/support.php as this bug system
is not the
appropriate forum for asking support questions. Due to the volume
of reports we can not explain in detail here why your report is not
a bug. The support channels will be able to provide an explanation
for you.
Thank you for your interest in PHP.
Setting ENV is not thread safe. No idea was this bug was kept so long
open/waiting for feedback. Also I cannot do anything against that :)
Previous Comments:
------------------------------------------------------------------------
[2005-10-25 16:06:32] hannu at lohtader dot com
I am currently tracing bug that is somehow related to sprintf with %d
parameters.
first it occured with dotproject project-environment, on line looking
like this (PEAR date package, format method):
$output .= sprintf("%02d",$this->month);
Again with phpmyadmin, file defines.lib.php line 47:
define('PMA_PHP_INT_VERSION', (int)sprintf('%d%02d%02d', $match[1],
$match[2], $match[3]));
I can not reproduce this just by creating new script, creating match
array and running that define - everything works just FINE!
Server is:
php version 4.4.0
Linux hostname 2.4.7-10 #1 Thu Sep 6 16:46:36 EDT 2001 i686
I was able to bypass this by installing dotproject to another server
with php 4.3.5 / Linux hostname 2.4.27-grs-smp #1 SMP Thu Sep 16
22:12:09 EEST 2004 i686
WHAT IS IMPORTANT is that I copy pasted from your code lines:
$year = 2005;
$month = 3;
$day = 24;
$time = '09:00';
$s = sprintf("%04d-%02d-%02dT%s:00", $year, $month, $day, $time);
to file defines.lib.php before line 47 and these lines from your code
made system just silently die in a same way that lines I have
presented. I have debugged this by using exit before and after these
problem lines.
So your lines made the same error I am tracing. Error is that nothing
is returned to the browser. Script just silently dies on calling
sprintf. So we are getting at least some hint that your error is also
sprintf -related!
I am totally confused what causes this. I do not know if this is php
bug, but wanted to comment it here to make some more glues to anyone
having this problem.
------------------------------------------------------------------------
[2005-05-07 01:00:04] 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".
------------------------------------------------------------------------
[2005-04-29 13:04:06] tony2001@php.net
Please try using this CVS snapshot:
http://snaps.php.net/php4-STABLE-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php4-win32-STABLE-latest.zip
Is it still reproducible ?
If yes, is it reproducible on NON-win32 systems ?
------------------------------------------------------------------------
[2005-04-08 01:23:40] rob at wildlime dot com
Any chance of PHP catching the exception in putenv/gettenv and chucking
a more informative error? Would help anyone else who hits this problem.
------------------------------------------------------------------------
[2005-04-08 00:27:12] sniper@php.net
Pierre promised to look into this..(or rather bogus this with good
explanation..)
------------------------------------------------------------------------
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/32422
--
Edit this bug report at http://bugs.php.net/?id=32422&edit=1