[cl-gd-devel] thread safety in cl-gd
Alain Picard
Alain.Picard at memetrics.com
Mon Jul 30 04:17:08 UTC 2007
Edi Weitz <edi at agharta.de> writes:
>
> But this shouldn't be the reason for segfaults, should it? I'm
> wondering if libgd itself is thread-safe. From
>
> http://www.libgd.org/Main_Page
>
> it doesn't necessarily look as if it is.
The GD manual states:
What's new in version 2.0.16?
* Thread safety for freetype text output. Background: all gd
functions were already thread safe, as long as only one thread
manipulates each image -- except for gdImageStringFT and
gdImageStringFTEx.
and I'm only interested in having 1 lisp thread at a time
manipulate an instance of CL-GD:*DEFAULT-IMAGE*, so it _seems_ to
me that it's supposed to be OK.
If I can't track down the segfaults, I might have to serialize all
entry points into my image generation routines, which won't really
be a problem in practice for my application.
Oh, and thanks for the quick fix!
-alain
More information about the Cl-gd-devel
mailing list