ID: 28431 User updated by: mastabog at hotmail dot com Reported By: mastabog at hotmail dot com Status: Closed Bug Type: Reproducible crash Operating System: WinXP PHP Version: 5CVS-2004-05-18 (dev) New Comment:
The next 2 CVS versions that i've downloaded *after* i received the bug-fix email still contained the bug. The one i've downloaded 10 minutes ago seems to work fine. I have even tested exif and gd functions and they work. I will leave the bug as closed and will open it only if the problems reappears in future cvs versions. p.s. what was exactly happening? It seemed like parts of the module were already pre-loaded... Previous Comments: ------------------------------------------------------------------------ [2004-05-18 17:27:25] [EMAIL PROTECTED] This bug has been fixed in CVS. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. This should be fixed now; please try the next snapshot dated after this entry. ------------------------------------------------------------------------ [2004-05-18 13:33:24] mastabog at hotmail dot com Description: ------------ Starting a few days ago (on friday, may 14th i think) my apache under winxp won't start if the gd2, mb_string and exif modules (maybe other too) are activated. Please note that this is recent, and I have not modified the php.ini nor the apache's httpd.conf files (i have also checked for updated in the php.ini-recommanded). The Apache2 (mine is 2.0.49) won't start and outputs the known apache's pop-up crash window with 'debug' and 'close' and the php.log file inside apache's dir states that: ---- [18-May-2004 13:16:17] PHP Notice: Constant MB_OVERLOAD_MAIL already defined in Unknown on line 0 ---- The Apache1.x (mine is 1.3.31) starts then dies afterwards with a generic crash pop-up window (application error, the memory could not be read .....) and the php.log file has more entries: ---- [18-May-2004 13:10:06] PHP Notice: Constant MB_OVERLOAD_MAIL already defined in Unknown on line 0 [18-May-2004 13:10:06] PHP Notice: Constant MB_OVERLOAD_STRING already defined in Unknown on line 0 [18-May-2004 13:10:06] PHP Notice: Constant MB_OVERLOAD_REGEX already defined in Unknown on line 0 [18-May-2004 13:10:06] PHP Notice: Constant MB_CASE_UPPER already defined in Unknown on line 0 [18-May-2004 13:10:06] PHP Notice: Constant MB_CASE_LOWER already defined in Unknown on line 0 [18-May-2004 13:10:06] PHP Notice: Constant MB_CASE_TITLE already defined in Unknown on line 0 [18-May-2004 13:10:06] PHP Notice: Constant EXIF_USE_MBSTRING already defined in Unknown on line 0 ---- It just seems apache 1.3 goes over more notices than apache2, but still dies when a pae is requested. The same happens when trying to load the gd2 module, as follows: Apache2 dies again with an apache's pop-up crash window and php.log has: ---- [18-May-2004 13:22:48] PHP Notice: Constant IMG_GIF already defined in Unknown on line 0 ---- Apache1.x dies when starting thew service/executable as apche2 or later on when a page is requested and php.log has: ---- [18-May-2004 13:25:00] PHP Notice: Constant IMG_GIF already defined in Unknown on line 0 [18-May-2004 13:25:00] PHP Notice: Constant IMG_JPG already defined in Unknown on line 0 [18-May-2004 13:25:00] PHP Notice: Constant IMG_JPEG already defined in Unknown on line 0 .... ---- there are 60+ messages of constant IMG_<XXX> already defined .... Again apache1 goes over more php notices, but still dies. Something has surely changed in the latest php5 code causing this sudden reproducible crash ... and i badly needed both gd2 and exif ... Thanks for looking into it. Bogdan ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=28431&edit=1
