Re: T1lib thread safety
| From: | Shane Caraveo | Date: | Sun, 14 Apr 2002 07:35:12 +0000 |
| Subject: | Re: T1lib thread safety | ||
| References: | 1 2 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-82778@lists.php.net to get a copy of this message | ||
It would be nice to have it as a flag in the module, like the api numbers.
Shane
Stig S. Bakken wrote:
Should we print a warning at the end of configure listing what libraries you are trying to link with that we know are not thread safe? - Stig On Sat, 2002-04-13 at 07:00, Rasmus Lerdorf wrote:Just the tip of the iceberg. There are a bunch of libraries that PHP can talk to that are not threadsafe. It's going to take a while before Apache2+PHP is going to be useful. For GD specifically, yes we can put in some mutexes as I earlier today put a copy of the GD library into PHP CVS so we can fiddle with it and distribute our own modified GD with PHP. -Rasmus On Sat, 13 Apr 2002, Brian Havard wrote:While doing some testing with Apache 2.0.35+PHP4.2.0RC3 I'm getting random crashes in T1_LoadFont(). Looking through the t1lib source (v1.3.1) I see frequent use of global variables which suggests it isn't thread safe. Is this a known problem? Maybe some mutexes in GD would help.... -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php