PHP 4.0 Bug #6528 Updated: shared memory foult

ID: 6528 User Update by: sozzi@netw.it Status: Feedback Bug Type: *General Issues Description: shared memory foult > Have you tried PHP4.0.3pl1? > Does this problem exist with it? No, I actually didn't: however we are going to upgrade to PHP4.0.3pl1 soon. I analyzed the problem in a more serious way and found the cause in allocation of arrays. I place an array (lets's say of n integers) in shared memory ... after an impredictable amount if time (from some hours to a couple of days) the function shm_get_var() gives a warning about "not enought shared memory". Function sizeof() shows that the array seems to contain more than n elements ... lets's say m ... where m * sizeof int is greater than memory allocated. The first n-elements readed by shm_get_var() however are the right ones. I perform about 1 access for second , where every operation is protected by semaphores. Thanks for attention -- andrea Previous Comments: --------------------------------------------------------------------------- [2000-11-01 11:22:56] derick@php.net I forwarded this bugreport to the creators of this extension. --------------------------------------------------------------------------- [2000-11-01 11:03:09] sniper@php.net Have you tried PHP4.0.3pl1? Does this problem exist with it? --Jani --------------------------------------------------------------------------- [2000-09-04 07:41:37] sozzi@netw.it Shared memory managed with standard php calls (shm_attach(), shm_get_var() etc. ) gets corrupted after some hours after initialization. On the same system shared memory managed with standard C calls from linux library is stable. Configure line is: configure --with-mysql --with-apache=../apache_1.3.12 --enable-track-vars --enable-sysvsh --------------------------------------------------------------------------- Full Bug description available at: http://bugs.php.net/?id=6528