PHP 4.0 Bug #5186 Updated: Certain combinations of session actions lead to segfault

ID: 5186 Updated by: sniper Reported By: mnc@firmseek.com Status: Closed Bug Type: Reproduceable crash Assigned To: Comments: Can not reproduce this crash with latest CVS. Please reopen this bug report if problem still exists with php4.0.2 or latest CVS or snapshot from http://snaps.php.net/ and include a bactrace of the crash. (André: Why was this set to Suspended?) --Jani Previous Comments: [2000-07-27 22:23:00] waldschrott@php.net doesn´t crash me on register_globals=off,tracking_vars=on (win32), I assume, you´re both running on register_globals=on ? --------------------------------------------------------------------------- [2000-07-27 21:23:52] jalal@php.net <? function crash() { global $x; global $HTTP_SESSION_VARS; session_start(); session_register('x'); $x++; } crash(); print "value is $x"; ?> This causes a crash here, but by commenting out the $HTTP_SESSION_VARS, it no longer crashes. Is this something that needs looking into? Or does it come under the heading of wrong usage? --------------------------------------------------------------------------- [2000-06-22 06:36:57] mnc@firmseek.com Here's code that reliably causes a segfault on all of our servers (as well as those of another user on the PHP-general mailing list). You may need to run it twice (so the session variable exists on disk) to generate the crash. <? function crash() { global $x, $HTTP_SESSION_VARS; session_start(); session_register('x'); $x++; } crash(); print "value is $x"; ?> --------------------------------------------------------------------------- Full Bug description available at: http://bugs.php.net/?id=5186