Date: Sun, 24 Jul 2005 21:43:31 +0200 (CEST) From: Werner LEMBERG <wl@gnu.org> To: marcus@FreeBSD.org Cc: gnome@FreeBSD.org, hintak_leung@yahoo.co.uk, cloos@jhcloos.com, freetype-devel@nongnu.org Subject: Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10 Message-ID: <20050724.214331.78488975.wl@gnu.org> In-Reply-To: <1122231108.16098.1.camel@shumai.marcuscom.com> References: <m3fyu4w5kc.fsf@lugabout.cloos.reno.nv.us> <20050724.203729.118957853.wl@gnu.org> <1122231108.16098.1.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > My test of the freetype module showed that I could cause a crash
> > > by loading any -iso10646-1 ttf font I tried; but using an eight
> > > bit encoding never caused a crash. I didn't try any other
> > > sixteen bit encodings (such as legacy CJK encodings) and I
> > > didn't try otf or type1 fonts in that test.
> >
> > Thanks for all your tests, but to really find out the problem we
> > need backtraces, which I was told is not an easy thing with X.
>
> We have one in my original report. It has full debugging symbols,
> and shows exactly where in xorg the symbol is being dereferenced.
There are two problems. The one with your backtrace shows that this
particular xorg version uses an internal function of FreeType which
has changed. I think David T. can answer this better (after returning
from his vacation) since he has already written some patches for main
applications to avoid FreeType internals.
The other problem (reported by James) could be a different bug,
probably in the cmap code of FreeType, and for his particular problem
I would like to see a backtrace.
Werner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050724.214331.78488975.wl>