#28568 [Asn->Csd]: known_post_content_types is not thread safe
| From: | moriyoshi@php.net | Date: | Mon, 21 Feb 2005 15:17:23 +0000 |
| Subject: | #28568 [Asn->Csd]: known_post_content_types is not thread safe | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-74335@lists.php.net to get a copy of this message | ||
ID: 28568
Updated by: moriyoshi@php.net
Reported By: novicky at aarongroup dot cz
-Status: Assigned
+Status: Closed
Bug Type: Reproducible crash
Operating System: win32
PHP Version: 4.3.7RC1
Assigned To: moriyoshi
New Comment:
This bug has been fixed in CVS.
Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
Thank you for the report, and for helping us make PHP better.
The fix will be in the upcoming release of PHP5.1.0
Previous Comments:
------------------------------------------------------------------------
[2004-07-12 18:56:44] moriyoshi@php.net
Verified. This needs to be fixed.
------------------------------------------------------------------------
[2004-07-06 01:39:14] sniper@php.net
correct nick
------------------------------------------------------------------------
[2004-05-31 12:21:07] derick@php.net
We can not add new globals in PHP 4 due to BC issues, but this can be
fixed for PHP 5. Assigning to the maintainer.
------------------------------------------------------------------------
[2004-05-31 07:57:14] novicky at aarongroup dot cz
It does change at least in MBSTRING module where post handlers are
being registered.
We have debugged crash of PHP as IIS isapi module and there was a
problem with different threads manipulates the same memory of
known_post_content_types.
------------------------------------------------------------------------
[2004-05-30 19:47:30] iliaa@php.net
It is safe because it does not actually change.
------------------------------------------------------------------------
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/28568
--
Edit this bug report at http://bugs.php.net/?id=28568&edit=1