#33011 [Fbk->Opn]: shmop: can still open segment for reading after shmop_delete

ID: 33011 User updated by: joe at bs0 dot com Reported By: joe at bs0 dot com -Status: Feedback +Status: Open Bug Type: Semaphore related Operating System: windows xp PHP Version: 5.0.4, 4.3.11 New Comment: patch: http://www.bs0.com/~joe/php/tsrm/tsrm_win32.diff complete: http://www.bs0.com/~joe/php/tsrm/tsrm_win32.c changes: http://www.bs0.com/~joe/php/tsrm/changes.txt Previous Comments: ------------------------------------------------------------------------ [2005-05-18 14:29:34] derick@php.net Put a patch on the web, and provide the URL here please. (And if you can, provide a summary why it was wrong and how you fixed it). ------------------------------------------------------------------------ [2005-05-18 13:24:45] joe at bs0 dot com no, php has a layer over the win32 api that provides an interface identical to the posix shm api. please see TSRM/tsrm_win32.c. The problem lies in this code, not in the windows code base. I have code working that fixes this problem, can you tell me how I can submit a patch/ if there is anyone that could do a code review? Thanks ------------------------------------------------------------------------ [2005-05-18 12:40:52] tony2001@php.net Bug Micro$oft about it. If it works on *nix and doesn't work on Windows, than it's definitely not a PHP problem, because PHP uses the same code in ext/shmop for all OSes. ------------------------------------------------------------------------ [2005-05-16 14:35:16] joe at bs0 dot com you are testing this under windows? ------------------------------------------------------------------------ [2005-05-16 12:24:09] tony2001@php.net This code outputs for me: shared memory block marked for deletion. block closed. PHP Warning: shmop_open(): unable to attach or create shared memory segment in /www/index.php on line 27 Warning: shmop_open(): unable to attach or create shared memory segment in /www/index.php on line 27 Could not open previously deleted block. ------------------------------------------------------------------------ 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/33011 -- Edit this bug report at http://bugs.php.net/?id=33011&edit=1