[cairo] Quartz regression in release 1.12

[cu]

Andrea,

Here is the backtrace:

Breakpoint 1, _cairo_error (status=CAIRO_STATUS_SURFACE_TYPE_MISMATCH)
at cairo-error.c:68
68        assert (_cairo_status_is_error (status));
(gdb) bt
#0  _cairo_error (status=CAIRO_STATUS_SURFACE_TYPE_MISMATCH) at
cairo-error.c:68
#1  0x0006ef85 in cairo_surface_unmap_image (surface=0x30ad10,
image=0x30c830) at cairo-surface.c:721
#2  0x0001f368 in _cairo_fallback_compositor_glyphs
(_compositor=0x1ab31c, extents=0xbfffd05c, scaled_font=0x805400,
glyphs=0xbfffdc94, num_glyphs=4, overlap=0) at
cairo-fallback-compositor.c:166
#3  0x0001ad6c in _cairo_compositor_glyphs (compositor=0x1ab808,
surface=0x30ad10, op=CAIRO_OPERATOR_OVER, source=0xbfffe6ac,
glyphs=0xbfffdc94, num_glyphs=4, scaled_font=0x805400, clip=0x0) at
cairo-compositor.c:246
#4  0x0008292c in _cairo_quartz_surface_glyphs (surface=0x30ad10,
op=CAIRO_OPERATOR_OVER, source=0xbfffe6ac, glyphs=0xbfffdc94,
num_glyphs=4, scaled_font=0x805400, clip=0x0) at cairo-quartz-surface.c:2159
#5  0x0006dc9b in _cairo_surface_show_text_glyphs (surface=0x30ad10,
op=CAIRO_OPERATOR_OVER, source=0xbfffe6ac, utf8=0x0, utf8_len=0,
glyphs=0xbfffdc94, num_glyphs=4, clusters=0x0, num_clusters=0,
cluster_flags=0, scaled_font=0x805400, clip=0x0) at cairo-surface.c:2330
#6  0x00025dff in _cairo_gstate_show_text_glyphs (gstate=0x81b620,
glyphs=0xbffff018, num_glyphs=4, info=0x0) at cairo-gstate.c:1968
#7  0x000123f9 in cairo_show_text (cr=0x81b600, utf8=0x190f60 "TEST") at
cairo.c:3257
#8  0x00003620 in main () at ci.c:20

Andrea Canciani wrote:
> I compiled libcairo.a and ignored the errors I get when building
> cairo-test-suite (a bunch of missing symbols from
> ApplicationServices; I guess there is some libtool magic missing in
> order to get the framework linked in when building with
> --disable-shared).
> When linking your bug.c against this library it prints Status: 0 (so I
> still cannot reproduce).
> Could you try to run the program in a debugger and break on _cairo_error?
> It should break exactly when the error status is generated, so the
> stack trace should provide useful information to find out what cairo
> is attempting and why it is failing.
>