#19243 [Opn]: Seg Fault Restoring Session Variables with References to Objects

From: Date: Fri, 06 Sep 2002 13:16:38 +0000
Subject: #19243 [Opn]: Seg Fault Restoring Session Variables with References to Objects
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-18574@lists.php.net to get a copy of this message
ID: 19243 User updated by: fdruseikis@sc.rr.com Reported By: fdruseikis@sc.rr.com Status: Open Bug Type: Session related Operating System: Linux RH 7.0 PHP Version: 4.2.2 New Comment: Also: doesn't save/restore arrays either. Previous Comments: ------------------------------------------------------------------------ [2002-09-06 08:03:59] fdruseikis@sc.rr.com I tried the script on this build: php4-200209060300 (linux) No segfault. However, both variables $o1 and $o2 are saved (and restored) as null. This results in a "Fatal Error: Call to a member function on a non-object in ..." Both $o1 and $o2 should refer to the original (singleton) object instance. ------------------------------------------------------------------------ [2002-09-05 16:48:14] kalowsky@php.net keeping set as feedback ------------------------------------------------------------------------ [2002-09-05 16:41:24] fdruseikis@sc.rr.com I'll give it a try. ------------------------------------------------------------------------ [2002-09-05 15:48:06] sniper@php.net Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip ------------------------------------------------------------------------ [2002-09-05 15:04:16] kalowsky@php.net Can you try one of the new snapshots please? There has been some work on the way sessions are delt with, and while I don't think it fixes this problem... hey it's worth a shot. Regardless, I don't think what you're doing is really going to ever work. I agree with yohgaki that we should throw some warnings or something. ------------------------------------------------------------------------ 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/19243 -- Edit this bug report at http://bugs.php.net/?id=19243&edit=1

« previous php.bugs (#18574) next »