Hmm. We (Bernard Blackham mainly) debugged this and came up with the
following:

 * freetype uses setjmp()
 * freetype was built against libc 2.3.4, using the symbol
   _setjmp@@GLIBC_2.3.4
 * I was building my program against libc 2.3.5

Apparently that code segfaulted because the setjmp buffer changed in
between libc 2.3.4 and 2.3.5, but this ABI incompatible change wasn't
correctly marked in the libc causing the new libc to still export the
old interface, or something like that. Or maybe the new libc still
exports the correct older interface as well as the new one, but the new
function got linked.

Something like that. It turns out then that rebuilding freetype against
the new libc fixes the issue.

johannes

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to