#32422 [Asn]: Access Violation on calling PEAR Date::before

ID: 32422 User updated by: rob at wildlime dot com Reported By: rob at wildlime dot com Status: Assigned Bug Type: Reproducible crash Operating System: Windows XP SP2 PHP Version: 4.3.10 Assigned To: pierre New Comment: Any chance of PHP catching the exception in putenv/gettenv and chucking a more informative error? Would help anyone else who hits this problem. Previous Comments: ------------------------------------------------------------------------ [2005-04-08 00:27:12] sniper@php.net Pierre promised to look into this..(or rather bogus this with good explanation..) ------------------------------------------------------------------------ [2005-04-06 05:52:25] rob at wildlime dot com Looks like this bug has been encountered before: http://pear.php.net/bugs/bug.php?id=2344 .. but the Date package owners maintain that it's not their problem. (Dunno how I didn't find that earlier :-/ I did search the bug DBs before posting, honest!) ------------------------------------------------------------------------ [2005-04-06 04:23:22] rob at wildlime dot com btw, the extensions loaded before were the ones packaged with PHP5, not old 4.3.10 ones! ------------------------------------------------------------------------ [2005-04-06 04:21:17] rob at wildlime dot com sorry for the delay... using PHP/5.1.0-dev - no extensions loaded - PEAR installed (default packages and Date) Got the same access violation. stack trace: ntdll!RtlpCoalesceFreeBlocks+0x21 ntdll!RtlFreeHeap+0x2e9 msvcrt!free+0xc3 msvcrt!__crtsetenv+0x193 msvcrt!_putenv_lk+0x42 msvcrt!_putenv+0x20 WARNING: Stack unwind information not available. Following frames may be wrong. php5ts!php_get_inf+0x1083 ------------------------------------------------------------------------ [2005-03-31 08:16:01] sniper@php.net Using extensions from different PHP version will not work of course.. but does the PEAR crap work any better? ------------------------------------------------------------------------ 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