My educated guess is that 0xb78086a0 is an error surface, on which we attempt to initialize the font_options, hence the SIGSEGV.
Can you test this? (If I am right, you still won't see the desired result but the crash should be resolved.)
commit c73b3e43e120065e40d8fc48c9bdbd88ebe8ab40
Author: Chris Wilson <email address hidden>
Date: Tue Aug 12 21:21:20 2008 +0100
[cairo-surface] Check for the error surface in _get_font_options()
cairo_surface_get_font_options() has the side effect of initialising the
font options on the surface, but fails to check that the surface is
valid first. Therefore if we are passed a read-only error object, we will
trigger a segmentation fault.
My educated guess is that 0xb78086a0 is an error surface, on which we attempt to initialize the font_options, hence the SIGSEGV.
Can you test this? (If I am right, you still won't see the desired result but the crash should be resolved.)
commit c73b3e43e120065 e40d8fc48c9bdbd 88ebe8ab40
Author: Chris Wilson <email address hidden>
Date: Tue Aug 12 21:21:20 2008 +0100
[cairo-surface] Check for the error surface in _get_font_options()
cairo_ surface_ get_font_ options( ) has the side effect of initialising the
font options on the surface, but fails to check that the surface is
valid first. Therefore if we are passed a read-only error object, we will
trigger a segmentation fault.
Most likely this is the bug behind: bugs.freedeskto p.org/show_ bug.cgi? id=17096.
http://