[cairo] [cairo-commit] font_freeze changes

[Carl Worth]

On Wed, 2008-10-22 at 20:57 +0100, Chris Wilson wrote:
> I felt is was redundant with the CAIRO_MUTEX_UNLOCK, since an attempt to
> unlock will be caught and it added no further documentation value.

Fair enough.

> > I'm feeling quite nervous seeing all these locking changes go by just as
> > we're trying to push 1.8.2 out the door. :-/
> 
> I've tested image/pdf/ps/svg/test*/xlib under linux and I'm confident
> about the locking there (well, for all the code paths covered by the
> test suite). I've run make check under win32 as well, but I haven't yet
> tried that under memfault/lockdep yet (since valgrind is a linux mostly
> tool, that will require running valgrind on the wine binaries). Quartz
> I've not even tried compiling, for lack of a host.

Yes. This is exactly the kind of testing we've had in the past and that
has led to a 1.x.0 release with broken mutex code for cairo-win32.

Any volunteers for testing? Would it help if I sent out a snapshot tar
file?

-Carl

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.cairographics.org/archives/cairo/attachments/20081022/89deda09/attachment.pgp