[ft-devel] Re: xorg crashes with freetype2-2.1.10
On Sun, 17 Jul 2005 15:24:40 -0500, Joe Marcus Clarke <[EMAIL PROTECTED]> wrote: Looks like the freetype module in xorg (and XFree86) makes reference to SFNT_Service->find_sbit_image which is now 0 in FT 2.1.10 (it used to be initialized to tt_find_sbit_image). This causes X to die rather abruptly when trying to dereference this symbol: http://people.freebsd.org/~mezz/gdb/gdb-freetype2.txt I assume this was done by design in FT (though I couldn't find a commit message that said spoke about this particular change). If so, what should X be doing to correctly obtain the glyph sbit? Thanks! I have solved the crash. I have been using it for the thirty minutes and no crash so far. If I do unpatch and it will crash within five minutes. Here's patch to put in freetype2/files. Don't know if patch is right, but at least it's fixed for me. http://people.freebsd.org/~mezz/patch-src::sfnt::sfdriver.c I found it by compared freetype2 2.1.9 and 2.1.10, you can check if you want to see for youself. I removed compare of Makefile, configure and other useless stuff. http://people.freebsd.org/~mezz/freetype2-compare.diff.bz2 It looks like 2.1.10 removed or disabled *find_sbit_image? Search for 'find_sbit_image' in freetype2-compare.diff.bz2. Cheers, Mezz Joe -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
The ChangeLog entry does mention the specific change explicitly: 2005-02-28 David Turner <[EMAIL PROTECTED]> ... * src/sfnt/sfdriver.c (sfnt_interface) [TT_CONFIG_OPTION_EMBEDDED_BITMAPS]: Don't use `tt_find_sbit_image' and `tt_load_sbit_metrics'. ... So the change is intentional. I just upgraded to stock freetype 2.1.10 (was using cvs-2004-dec-31), went around a few web pages with mozilla-xft, and I don't have crashes. I am using xorg 6.8.2 on linux. How do you trigger the crash? Joe Marcus Clarke wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hin-Tak Leung wrote: | Found the CVS entry: | | http://savannah.nongnu.org/cgi-bin/viewcvs/freetype/freetype2/src/sfnt/sfdriver.c.diff?r1=1.71&r2=1.72 | | | | * include/freetype/internal/tttypes.h, src/sfnt/ttsbit.c, | src/sfnt/ttsbit0.c, | src/truetype/ttobjs.c, src/cff/cffobjs.c, src/sfnt/sfobjs.c: | implementing new | heap-optimized embedded bitmap loader. This one also fixes bug #12107 | | checked in by user 'freetype' (David Turner?). they were changed to NULL, | then to zero - there must be a reason? Yes, there must be a reason, but that commit message doesn't list sfdriver.c explicitly. That's why I was wondering what the exact reason was for the change, and what new steps should be done to get similar results from FT. Joe | | Jeremy Messenger wrote: | |> On Sun, 17 Jul 2005 15:24:40 -0500, Joe Marcus Clarke |> <[EMAIL PROTECTED]> wrote: |> |>> Looks like the freetype module in xorg (and XFree86) makes reference to |>> SFNT_Service->find_sbit_image which is now 0 in FT 2.1.10 (it used to be |>> initialized to tt_find_sbit_image). This causes X to die rather |>> abruptly when trying to dereference this symbol: |>> |>> http://people.freebsd.org/~mezz/gdb/gdb-freetype2.txt |>> |>> I assume this was done by design in FT (though I couldn't find a commit |>> message that said spoke about this particular change). If so, what |>> should X be doing to correctly obtain the glyph sbit? Thanks! |> |> |> |> I have solved the crash. I have been using it for the thirty minutes |> and no crash so far. If I do unpatch and it will crash within five |> minutes. Here's patch to put in freetype2/files. Don't know if patch |> is right, but at least it's fixed for me. |> |> http://people.freebsd.org/~mezz/patch-src::sfnt::sfdriver.c |> |> I found it by compared freetype2 2.1.9 and 2.1.10, you can check if |> you want to see for youself. I removed compare of Makefile, configure |> and other useless stuff. |> |> http://people.freebsd.org/~mezz/freetype2-compare.diff.bz2 |> |> It looks like 2.1.10 removed or disabled *find_sbit_image? Search for |> 'find_sbit_image' in freetype2-compare.diff.bz2. |> |> Cheers, |> Mezz |> |>> Joe |> |> |> |> | | | ___ How much | free photo storage do you get? Store your holiday snaps for FREE with | Yahoo! Photos http://uk.photos.yahoo.com | - -- Joe Marcus Clarke FreeBSD GNOME Team::[EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC3W+rb2iPiv4Uz4cRArfoAJ4tP/XRPRwWykuQL+DZmGldgwCBOgCfZrNl ts1bAb9rB9D1InM6I8QuhcA= =T1sX -END PGP SIGNATURE- ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
Joe Marcus Clarke wrote: Ours is autogenerated by ttmkfdir. You might fine some helpful hints on crashing X from this thread: http://forums.gentoo.org/viewtopic-t-359535-highlight-aalib.html?sid=58ed6c452268c0e3f213df9db314ee45. hmm, don't have ttmkfdir (or ttfmkdir, or mkttfdir), but mkfontdir is shipped with xorg. Still can't crash X - tried gtk mplayer. My LANG is unset, LC_COLLATE=C , LC_ALL=C , but I have plenty of CJK fonts, the Arphic chinese ones and the microsoft chinese and japanese ones - and I specifically tried CJK web pages earlier with mozilla. No crashes so far. What version of xorg is your user using? ___ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
Joe Marcus Clarke wrote: On Wed, 2005-07-20 at 06:16 +0100, Hin-Tak Leung wrote: The ChangeLog entry does mention the specific change explicitly: Ah. Still kind of cryptic, though. _Why_ shouldn't they be used? Well, not entirely cryptic - seems to be a rewrite with an 'enhanced bitmap loader' for the changes in the same group. 2005-02-28 David Turner <[EMAIL PROTECTED]> ... * src/sfnt/sfdriver.c (sfnt_interface) [TT_CONFIG_OPTION_EMBEDDED_BITMAPS]: Don't use `tt_find_sbit_image' and `tt_load_sbit_metrics'. ... So the change is intentional. I just upgraded to stock freetype 2.1.10 (was using cvs-2004-dec-31), went around a few web pages with mozilla-xft, and I don't have crashes. I am using xorg 6.8.2 on linux. How do you trigger the crash? Honestly, I have been able to trigger the crash myself. It appears to be triggered by a certain font (or set of fonts). The Microsoft webfonts seem to be particularly problematic. I have the microsoft fonts, actually, and I just changed mozilla-xft to use specifically courier new (the one in your gdb backtrace) for display. No crashes yet. Granted, mozilla-xft probably used it differently - *how* do you trigger a crash? You do realise the font name is quite broken (seems to be followed by garbage all the time) in your gdb bt? "-webfonts-courier new-medium..." may worth checking your font.dir - seems to be hand-edited - mine is auto-generated by mkfontdir, and entry start with e.g. "-microsoft-courier new-..." Joe Joe Marcus Clarke wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hin-Tak Leung wrote: | Found the CVS entry: | | http://savannah.nongnu.org/cgi-bin/viewcvs/freetype/freetype2/src/sfnt/sfdriver.c.diff?r1=1.71&r2=1.72 | | | | * include/freetype/internal/tttypes.h, src/sfnt/ttsbit.c, | src/sfnt/ttsbit0.c, | src/truetype/ttobjs.c, src/cff/cffobjs.c, src/sfnt/sfobjs.c: | implementing new | heap-optimized embedded bitmap loader. This one also fixes bug #12107 | | checked in by user 'freetype' (David Turner?). they were changed to NULL, | then to zero - there must be a reason? Yes, there must be a reason, but that commit message doesn't list sfdriver.c explicitly. That's why I was wondering what the exact reason was for the change, and what new steps should be done to get similar results from FT. Joe | | Jeremy Messenger wrote: | |> On Sun, 17 Jul 2005 15:24:40 -0500, Joe Marcus Clarke |> <[EMAIL PROTECTED]> wrote: |> |>> Looks like the freetype module in xorg (and XFree86) makes reference to |>> SFNT_Service->find_sbit_image which is now 0 in FT 2.1.10 (it used to be |>> initialized to tt_find_sbit_image). This causes X to die rather |>> abruptly when trying to dereference this symbol: |>> |>> http://people.freebsd.org/~mezz/gdb/gdb-freetype2.txt |>> |>> I assume this was done by design in FT (though I couldn't find a commit |>> message that said spoke about this particular change). If so, what |>> should X be doing to correctly obtain the glyph sbit? Thanks! |> |> |> |> I have solved the crash. I have been using it for the thirty minutes |> and no crash so far. If I do unpatch and it will crash within five |> minutes. Here's patch to put in freetype2/files. Don't know if patch |> is right, but at least it's fixed for me. |> |> http://people.freebsd.org/~mezz/patch-src::sfnt::sfdriver.c |> |> I found it by compared freetype2 2.1.9 and 2.1.10, you can check if |> you want to see for youself. I removed compare of Makefile, configure |> and other useless stuff. |> |> http://people.freebsd.org/~mezz/freetype2-compare.diff.bz2 |> |> It looks like 2.1.10 removed or disabled *find_sbit_image? Search for |> 'find_sbit_image' in freetype2-compare.diff.bz2. |> |> Cheers, |> Mezz |> |>> Joe |> |> |> |> | | | ___ How much | free photo storage do you get? Store your holiday snaps for FREE with | Yahoo! Photos http://uk.photos.yahoo.com | - -- Joe Marcus Clarke FreeBSD GNOME Team::[EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC3W+rb2iPiv4Uz4cRArfoAJ4tP/XRPRwWykuQL+DZmGldgwCBOgCfZrNl ts1bAb9rB9D1InM6I8QuhcA= =T1sX -END PGP SIGNATURE- ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
Joe Marcus Clarke wrote: On Wed, 2005-07-20 at 07:02 +0100, Hin-Tak Leung wrote: Joe Marcus Clarke wrote: Ours is autogenerated by ttmkfdir. You might fine some helpful hints on crashing X from this thread: http://forums.gentoo.org/viewtopic-t-359535-highlight-aalib.html?sid=58ed6c452268c0e3f213df9db314ee45. hmm, don't have ttmkfdir (or ttfmkdir, or mkttfdir), but mkfontdir is shipped with xorg. Still can't crash X - tried gtk mplayer. My LANG is unset, LC_COLLATE=C , LC_ALL=C , but I have plenty of CJK fonts, the Arphic chinese ones and the microsoft chinese and japanese ones - and I specifically tried CJK web pages earlier with mozilla. No crashes so far. What version of xorg is your user using? 6.8.2. You also need the freetype module loaded in X. yes, I Know that - how else can I view web pages with truetype fonts?! Curious problem. (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.so (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project" compiled for 6.8.2, module version = 2.1.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
Jeremy Messenger wrote: I have played with it more to find a good way to reproduce it. Well, kind of. Download crash.txt, then view in Firefox (maybe works for Mozilla too). Be sure to save anything before you play with crash.txt, because it will kill X. http://people.freebsd.org/~mezz/crash.txt To reproduce crash in Firefox: 1) Run Firefox (keep in mind, everything option is default) 2) Open crash.txt 3) Go to menu, 'View -> Character Encoding -> More Encodings -> Unicode' and select any in there. After you selected, then do it again but select different Unicode like more than three times. Sometime it would crash X in two changes. Tried all of them unicode (7-8 of them?) with mozilla-xft and my X-server just won't crash... ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
> "Hin-Tak" == Hin-Tak Leung <[EMAIL PROTECTED]> writes: >> You also need the freetype module loaded in X. Hin-Tak> yes, I Know that - how else can I view web pages with Hin-Tak> truetype fonts?! Mozilla uses client-side fonts via libXft. The crash in question is in the X server's freetype module which supports server-side fonts. You'll need to use an app which uses the (older) server-side font support to trigger the bug. An easy choice is xfd(1x) with a -fn option. Eg: xfd -fn -adobe-courier-medium-r-normal--0-0-100-100-m-0-iso10646-1 should trigger the bug if you have the freetype module loaded and an entry in a fonts.dir file in your fontpath that points that XLFD to a scalable font. -JimC -- James H. Cloos, Jr. <[EMAIL PROTECTED]> ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hin-Tak Leung wrote: | Found the CVS entry: | | http://savannah.nongnu.org/cgi-bin/viewcvs/freetype/freetype2/src/sfnt/sfdriver.c.diff?r1=1.71&r2=1.72 | | | | * include/freetype/internal/tttypes.h, src/sfnt/ttsbit.c, | src/sfnt/ttsbit0.c, | src/truetype/ttobjs.c, src/cff/cffobjs.c, src/sfnt/sfobjs.c: | implementing new | heap-optimized embedded bitmap loader. This one also fixes bug #12107 | | checked in by user 'freetype' (David Turner?). they were changed to NULL, | then to zero - there must be a reason? Yes, there must be a reason, but that commit message doesn't list sfdriver.c explicitly. That's why I was wondering what the exact reason was for the change, and what new steps should be done to get similar results from FT. Joe | | Jeremy Messenger wrote: | |> On Sun, 17 Jul 2005 15:24:40 -0500, Joe Marcus Clarke |> <[EMAIL PROTECTED]> wrote: |> |>> Looks like the freetype module in xorg (and XFree86) makes reference to |>> SFNT_Service->find_sbit_image which is now 0 in FT 2.1.10 (it used to be |>> initialized to tt_find_sbit_image). This causes X to die rather |>> abruptly when trying to dereference this symbol: |>> |>> http://people.freebsd.org/~mezz/gdb/gdb-freetype2.txt |>> |>> I assume this was done by design in FT (though I couldn't find a commit |>> message that said spoke about this particular change). If so, what |>> should X be doing to correctly obtain the glyph sbit? Thanks! |> |> |> |> I have solved the crash. I have been using it for the thirty minutes |> and no crash so far. If I do unpatch and it will crash within five |> minutes. Here's patch to put in freetype2/files. Don't know if patch |> is right, but at least it's fixed for me. |> |> http://people.freebsd.org/~mezz/patch-src::sfnt::sfdriver.c |> |> I found it by compared freetype2 2.1.9 and 2.1.10, you can check if |> you want to see for youself. I removed compare of Makefile, configure |> and other useless stuff. |> |> http://people.freebsd.org/~mezz/freetype2-compare.diff.bz2 |> |> It looks like 2.1.10 removed or disabled *find_sbit_image? Search for |> 'find_sbit_image' in freetype2-compare.diff.bz2. |> |> Cheers, |> Mezz |> |>> Joe |> |> |> |> | | | ___ How much | free photo storage do you get? Store your holiday snaps for FREE with | Yahoo! Photos http://uk.photos.yahoo.com | - -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC3W+rb2iPiv4Uz4cRArfoAJ4tP/XRPRwWykuQL+DZmGldgwCBOgCfZrNl ts1bAb9rB9D1InM6I8QuhcA= =T1sX -END PGP SIGNATURE- ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
Found the CVS entry: http://savannah.nongnu.org/cgi-bin/viewcvs/freetype/freetype2/src/sfnt/sfdriver.c.diff?r1=1.71&r2=1.72 * include/freetype/internal/tttypes.h, src/sfnt/ttsbit.c, src/sfnt/ttsbit0.c, src/truetype/ttobjs.c, src/cff/cffobjs.c, src/sfnt/sfobjs.c: implementing new heap-optimized embedded bitmap loader. This one also fixes bug #12107 checked in by user 'freetype' (David Turner?). they were changed to NULL, then to zero - there must be a reason? Jeremy Messenger wrote: On Sun, 17 Jul 2005 15:24:40 -0500, Joe Marcus Clarke <[EMAIL PROTECTED]> wrote: Looks like the freetype module in xorg (and XFree86) makes reference to SFNT_Service->find_sbit_image which is now 0 in FT 2.1.10 (it used to be initialized to tt_find_sbit_image). This causes X to die rather abruptly when trying to dereference this symbol: http://people.freebsd.org/~mezz/gdb/gdb-freetype2.txt I assume this was done by design in FT (though I couldn't find a commit message that said spoke about this particular change). If so, what should X be doing to correctly obtain the glyph sbit? Thanks! I have solved the crash. I have been using it for the thirty minutes and no crash so far. If I do unpatch and it will crash within five minutes. Here's patch to put in freetype2/files. Don't know if patch is right, but at least it's fixed for me. http://people.freebsd.org/~mezz/patch-src::sfnt::sfdriver.c I found it by compared freetype2 2.1.9 and 2.1.10, you can check if you want to see for youself. I removed compare of Makefile, configure and other useless stuff. http://people.freebsd.org/~mezz/freetype2-compare.diff.bz2 It looks like 2.1.10 removed or disabled *find_sbit_image? Search for 'find_sbit_image' in freetype2-compare.diff.bz2. Cheers, Mezz Joe ___ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
On Wed, 2005-07-20 at 02:11 -0400, Joe Marcus Clarke wrote: > On Wed, 2005-07-20 at 07:16 +0100, Hin-Tak Leung wrote: > > Joe Marcus Clarke wrote: > > > On Wed, 2005-07-20 at 07:02 +0100, Hin-Tak Leung wrote: > > > > > >>Joe Marcus Clarke wrote: > > >> > > >> > > >>>Ours is autogenerated by ttmkfdir. You might fine some helpful hints on > > >>>crashing X from this thread: > > >>>http://forums.gentoo.org/viewtopic-t-359535-highlight-aalib.html?sid=58ed6c452268c0e3f213df9db314ee45. > > >> > > >>hmm, don't have ttmkfdir (or ttfmkdir, or mkttfdir), but mkfontdir is > > >>shipped with xorg. Still can't crash X - tried gtk mplayer. > > >>My LANG is unset, LC_COLLATE=C , LC_ALL=C , > > >>but I have plenty of CJK fonts, the Arphic chinese ones and the microsoft > > >>chinese and japanese ones - and I specifically tried CJK web pages earlier > > >>with mozilla. No crashes so far. > > >> > > >>What version of xorg is your user using? > > > > > > > > > 6.8.2. You also need the freetype module loaded in X. > > > > yes, I Know that - how else can I view web pages with truetype fonts?! > > Curious problem. > > Font server. > > > > > (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.so > > (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project" > > compiled for 6.8.2, module version = 2.1.0 > > Module class: X.Org Font Renderer > > ABI class: X.Org Font Renderer, version 0.4 > > I guess one other thing to check is that libfreetype.so (the X module) > is linked to the correct version of freetype2. But in any event, the > code in X is clearly suspect, and reverting that change to Sent too soon. Reverting the change to sfdriver.c does make the reported problem go away. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
On Wed, 20 Jul 2005 00:16:52 -0500, Hin-Tak Leung <[EMAIL PROTECTED]> wrote: So the change is intentional. I just upgraded to stock freetype 2.1.10 (was using cvs-2004-dec-31), went around a few web pages with mozilla-xft, and I don't have crashes. I am using xorg 6.8.2 on linux. How do you trigger the crash? I have played with it more to find a good way to reproduce it. Well, kind of. Download crash.txt, then view in Firefox (maybe works for Mozilla too). Be sure to save anything before you play with crash.txt, because it will kill X. http://people.freebsd.org/~mezz/crash.txt To reproduce crash in Firefox: 1) Run Firefox (keep in mind, everything option is default) 2) Open crash.txt 3) Go to menu, 'View -> Character Encoding -> More Encodings -> Unicode' and select any in there. After you selected, then do it again but select different Unicode like more than three times. Sometime it would crash X in two changes. As for Opera, it's a lot easy. All I have to do is open crash.txt and X got crashed. My Opera option is heavy tweaked on fonts options by use Microsoft fonts mostly, bold and other options. I have no idea if it will crash with default option or without have non-Microsoft fonts installed. Cheers, Mezz -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
On Wed, 2005-07-20 at 06:16 +0100, Hin-Tak Leung wrote: > The ChangeLog entry does mention the specific change explicitly: Ah. Still kind of cryptic, though. _Why_ shouldn't they be used? > > 2005-02-28 David Turner <[EMAIL PROTECTED]> > ... > * src/sfnt/sfdriver.c (sfnt_interface) > [TT_CONFIG_OPTION_EMBEDDED_BITMAPS]: Don't use `tt_find_sbit_image' > and `tt_load_sbit_metrics'. > ... > > So the change is intentional. I just upgraded to stock freetype 2.1.10 > (was using cvs-2004-dec-31), went around a few web pages with mozilla-xft, > and I don't have crashes. I am using xorg 6.8.2 on linux. How do you > trigger the crash? Honestly, I have been able to trigger the crash myself. It appears to be triggered by a certain font (or set of fonts). The Microsoft webfonts seem to be particularly problematic. Joe > > Joe Marcus Clarke wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Hin-Tak Leung wrote: > > | Found the CVS entry: > > | > > | > > http://savannah.nongnu.org/cgi-bin/viewcvs/freetype/freetype2/src/sfnt/sfdriver.c.diff?r1=1.71&r2=1.72 > > > > > > > > | > > | > > | > > | * include/freetype/internal/tttypes.h, src/sfnt/ttsbit.c, > > | src/sfnt/ttsbit0.c, > > | src/truetype/ttobjs.c, src/cff/cffobjs.c, src/sfnt/sfobjs.c: > > | implementing new > > | heap-optimized embedded bitmap loader. This one also fixes bug #12107 > > | > > | checked in by user 'freetype' (David Turner?). they were changed to NULL, > > | then to zero - there must be a reason? > > > > Yes, there must be a reason, but that commit message doesn't list > > sfdriver.c explicitly. That's why I was wondering what the exact reason > > was for the change, and what new steps should be done to get similar > > results from FT. > > > > Joe > > > > | > > | Jeremy Messenger wrote: > > | > > |> On Sun, 17 Jul 2005 15:24:40 -0500, Joe Marcus Clarke > > |> <[EMAIL PROTECTED]> wrote: > > |> > > |>> Looks like the freetype module in xorg (and XFree86) makes reference to > > |>> SFNT_Service->find_sbit_image which is now 0 in FT 2.1.10 (it used > > to be > > |>> initialized to tt_find_sbit_image). This causes X to die rather > > |>> abruptly when trying to dereference this symbol: > > |>> > > |>> http://people.freebsd.org/~mezz/gdb/gdb-freetype2.txt > > |>> > > |>> I assume this was done by design in FT (though I couldn't find a commit > > |>> message that said spoke about this particular change). If so, what > > |>> should X be doing to correctly obtain the glyph sbit? Thanks! > > |> > > |> > > |> > > |> I have solved the crash. I have been using it for the thirty minutes > > |> and no crash so far. If I do unpatch and it will crash within five > > |> minutes. Here's patch to put in freetype2/files. Don't know if patch > > |> is right, but at least it's fixed for me. > > |> > > |> http://people.freebsd.org/~mezz/patch-src::sfnt::sfdriver.c > > |> > > |> I found it by compared freetype2 2.1.9 and 2.1.10, you can check if > > |> you want to see for youself. I removed compare of Makefile, configure > > |> and other useless stuff. > > |> > > |> http://people.freebsd.org/~mezz/freetype2-compare.diff.bz2 > > |> > > |> It looks like 2.1.10 removed or disabled *find_sbit_image? Search for > > |> 'find_sbit_image' in freetype2-compare.diff.bz2. > > |> > > |> Cheers, > > |> Mezz > > |> > > |>> Joe > > |> > > |> > > |> > > |> > > | > > | > > | ___ How much > > | free photo storage do you get? Store your holiday snaps for FREE with > > | Yahoo! Photos http://uk.photos.yahoo.com > > | > > > > > > - -- > > Joe Marcus Clarke > > FreeBSD GNOME Team::[EMAIL PROTECTED] > > FreeNode / #freebsd-gnome > > http://www.FreeBSD.org/gnome > > -BEGIN PGP SIGNATURE- > > Version: GnuPG v1.4.1 (Darwin) > > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > > > iD8DBQFC3W+rb2iPiv4Uz4cRArfoAJ4tP/XRPRwWykuQL+DZmGldgwCBOgCfZrNl > > ts1bAb9rB9D1InM6I8QuhcA= > > =T1sX > > -END PGP SIGNATURE- > > > > > > > ___ > Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with > voicemail http://uk.messenger.yahoo.com > -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
On Wed, 2005-07-20 at 07:02 +0100, Hin-Tak Leung wrote: > Joe Marcus Clarke wrote: > > > Ours is autogenerated by ttmkfdir. You might fine some helpful hints on > > crashing X from this thread: > > http://forums.gentoo.org/viewtopic-t-359535-highlight-aalib.html?sid=58ed6c452268c0e3f213df9db314ee45. > > hmm, don't have ttmkfdir (or ttfmkdir, or mkttfdir), but mkfontdir is > shipped with xorg. Still can't crash X - tried gtk mplayer. > My LANG is unset, LC_COLLATE=C , LC_ALL=C , > but I have plenty of CJK fonts, the Arphic chinese ones and the microsoft > chinese and japanese ones - and I specifically tried CJK web pages earlier > with mozilla. No crashes so far. > > What version of xorg is your user using? 6.8.2. You also need the freetype module loaded in X. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
On Wed, 2005-07-20 at 06:40 +0100, Hin-Tak Leung wrote: > Joe Marcus Clarke wrote: > > On Wed, 2005-07-20 at 06:16 +0100, Hin-Tak Leung wrote: > > > >>The ChangeLog entry does mention the specific change explicitly: > > > > > > Ah. Still kind of cryptic, though. _Why_ shouldn't they be used? > > Well, not entirely cryptic - seems to be a rewrite with an 'enhanced bitmap > loader' for the changes in the same group. > > >>2005-02-28 David Turner <[EMAIL PROTECTED]> > >>... > >> * src/sfnt/sfdriver.c (sfnt_interface) > >> [TT_CONFIG_OPTION_EMBEDDED_BITMAPS]: Don't use `tt_find_sbit_image' > >> and `tt_load_sbit_metrics'. > >>... > >> > >>So the change is intentional. I just upgraded to stock freetype 2.1.10 > >>(was using cvs-2004-dec-31), went around a few web pages with mozilla-xft, > >>and I don't have crashes. I am using xorg 6.8.2 on linux. How do you > >>trigger the crash? > > > > > > Honestly, I have been able to trigger the crash myself. It appears to > > be triggered by a certain font (or set of fonts). The Microsoft > > webfonts seem to be particularly problematic. > > I have the microsoft fonts, actually, and I just changed mozilla-xft to use > specifically courier new (the one in your gdb backtrace) for display. No > crashes yet. Granted, mozilla-xft probably used it differently - *how* do you > trigger a crash? You do realise the font name is quite broken (seems to be > followed by garbage all the time) in your gdb bt? This is not my crash dump. However, the user that can reproduce this crash can do so at will using Opera. > > "-webfonts-courier new-medium..." > > may worth checking your font.dir - seems to be hand-edited - mine > is auto-generated by mkfontdir, and entry start with e.g. > "-microsoft-courier new-..." Ours is autogenerated by ttmkfdir. You might fine some helpful hints on crashing X from this thread: http://forums.gentoo.org/viewtopic-t-359535-highlight-aalib.html?sid=58ed6c452268c0e3f213df9db314ee45. Joe > > > > > Joe > > > > > >>Joe Marcus Clarke wrote: > >> > >>>-BEGIN PGP SIGNED MESSAGE- > >>>Hash: SHA1 > >>> > >>>Hin-Tak Leung wrote: > >>>| Found the CVS entry: > >>>| > >>>| > >>>http://savannah.nongnu.org/cgi-bin/viewcvs/freetype/freetype2/src/sfnt/sfdriver.c.diff?r1=1.71&r2=1.72 > >>> > >>> > >>> > >>>| > >>>| > >>>| > >>>| * include/freetype/internal/tttypes.h, src/sfnt/ttsbit.c, > >>>| src/sfnt/ttsbit0.c, > >>>| src/truetype/ttobjs.c, src/cff/cffobjs.c, src/sfnt/sfobjs.c: > >>>| implementing new > >>>| heap-optimized embedded bitmap loader. This one also fixes bug #12107 > >>>| > >>>| checked in by user 'freetype' (David Turner?). they were changed to NULL, > >>>| then to zero - there must be a reason? > >>> > >>>Yes, there must be a reason, but that commit message doesn't list > >>>sfdriver.c explicitly. That's why I was wondering what the exact reason > >>>was for the change, and what new steps should be done to get similar > >>>results from FT. > >>> > >>>Joe > >>> > >>>| > >>>| Jeremy Messenger wrote: > >>>| > >>>|> On Sun, 17 Jul 2005 15:24:40 -0500, Joe Marcus Clarke > >>>|> <[EMAIL PROTECTED]> wrote: > >>>|> > >>>|>> Looks like the freetype module in xorg (and XFree86) makes reference to > >>>|>> SFNT_Service->find_sbit_image which is now 0 in FT 2.1.10 (it used > >>>to be > >>>|>> initialized to tt_find_sbit_image). This causes X to die rather > >>>|>> abruptly when trying to dereference this symbol: > >>>|>> > >>>|>> http://people.freebsd.org/~mezz/gdb/gdb-freetype2.txt > >>>|>> > >>>|>> I assume this was done by design in FT (though I couldn't find a commit > >>>|>> message that said spoke about this particular change). If so, what > >>>|>> should X be doing to correctly obtain the glyph sbit? Thanks! > >>>|> > >>>|> > >>>|> > >>>|> I have solved the crash. I have been using it for the thirty minutes > >>>|> and no crash so far. If I do unpatch and it will crash within five > >>>|> minutes. Here's patch to put in freetype2/files. Don't know if patch > >>>|> is right, but at least it's fixed for me. > >>>|> > >>>|> http://people.freebsd.org/~mezz/patch-src::sfnt::sfdriver.c > >>>|> > >>>|> I found it by compared freetype2 2.1.9 and 2.1.10, you can check if > >>>|> you want to see for youself. I removed compare of Makefile, configure > >>>|> and other useless stuff. > >>>|> > >>>|> http://people.freebsd.org/~mezz/freetype2-compare.diff.bz2 > >>>|> > >>>|> It looks like 2.1.10 removed or disabled *find_sbit_image? Search for > >>>|> 'find_sbit_image' in freetype2-compare.diff.bz2. > >>>|> > >>>|> Cheers, > >>>|> Mezz > >>>|> > >>>|>> Joe > >>>|> > >>>|> > >>>|> > >>>|> > >>>| > >>>| > >>>| ___ How much > >>>| free photo storage do you get? Store your holiday snaps for FREE with > >>>| Yahoo! Photos http://uk.photos.yahoo.com > >>>| > >>> > >>> > >>>- -- > >>>Joe Marcus Clarke > >>>FreeBSD GNOME Team::[EMAIL PROTECTED] > >>>Fr
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
On Wed, 2005-07-20 at 07:16 +0100, Hin-Tak Leung wrote: > Joe Marcus Clarke wrote: > > On Wed, 2005-07-20 at 07:02 +0100, Hin-Tak Leung wrote: > > > >>Joe Marcus Clarke wrote: > >> > >> > >>>Ours is autogenerated by ttmkfdir. You might fine some helpful hints on > >>>crashing X from this thread: > >>>http://forums.gentoo.org/viewtopic-t-359535-highlight-aalib.html?sid=58ed6c452268c0e3f213df9db314ee45. > >> > >>hmm, don't have ttmkfdir (or ttfmkdir, or mkttfdir), but mkfontdir is > >>shipped with xorg. Still can't crash X - tried gtk mplayer. > >>My LANG is unset, LC_COLLATE=C , LC_ALL=C , > >>but I have plenty of CJK fonts, the Arphic chinese ones and the microsoft > >>chinese and japanese ones - and I specifically tried CJK web pages earlier > >>with mozilla. No crashes so far. > >> > >>What version of xorg is your user using? > > > > > > 6.8.2. You also need the freetype module loaded in X. > > yes, I Know that - how else can I view web pages with truetype fonts?! > Curious problem. Font server. > > (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.so > (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project" > compiled for 6.8.2, module version = 2.1.0 > Module class: X.Org Font Renderer > ABI class: X.Org Font Renderer, version 0.4 I guess one other thing to check is that libfreetype.so (the X module) is linked to the correct version of freetype2. But in any event, the code in X is clearly suspect, and reverting that change to > > > > > ___ > Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with > voicemail http://uk.messenger.yahoo.com > -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
On Wed, 20 Jul 2005 00:39:56 -0500, Joe Marcus Clarke <[EMAIL PROTECTED]> wrote: On Wed, 2005-07-20 at 06:40 +0100, Hin-Tak Leung wrote: "-webfonts-courier new-medium..." may worth checking your font.dir - seems to be hand-edited - mine is auto-generated by mkfontdir, and entry start with e.g. "-microsoft-courier new-..." Ours is autogenerated by ttmkfdir. You might fine some helpful hints on crashing X from this thread: http://forums.gentoo.org/viewtopic-t-359535-highlight-aalib.html?sid=58ed6c452268c0e3f213df9db314ee45. Okay, I have played with it more.. Guess what? Hin-Tak is right about rename the name do cause the trouble for freetype2 2.1.10 with no patch. The old freetype2 do accept the rename but not now in freetype2 2.1.10. no-crash: Run those.. # cd /usr/X11R6/lib/X11/fonts/webfonts # rm fonts.* # mkfontscale # mkfontdir # fc-cache -f -v crash: Same way above, but rename all microsoft and monotype to webfonts. no-crash: Edit x11-fonts/webfonts/Makefile by remove the rename microsoft and monotype part. Just leave name default. crash: Leave x11-fonts/webfonts/Makefile alone and let rename microsoft and monotype to webfonts. I think I am going to modify webfonts to use mkfontscale and mkfontdir since it comes with xorg and remove the rename part. Then contact to the maintainer with patch. Cheers, Mezz -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
Jeremy Messenger wrote: On Wed, 20 Jul 2005 00:39:56 -0500, Joe Marcus Clarke Okay, I have played with it more.. Guess what? Hin-Tak is right about rename the name do cause the trouble for freetype2 2.1.10 with no patch. The old freetype2 do accept the rename but not now in freetype2 2.1.10. no-crash:Run those.. # cd /usr/X11R6/lib/X11/fonts/webfonts # rm fonts.* # mkfontscale # mkfontdir # fc-cache -f -v crash:Same way above, but rename all microsoft and monotype to webfonts. no-crash:Edit x11-fonts/webfonts/Makefile by remove the rename microsoft and monotype part. Just leave name default. crash:Leave x11-fonts/webfonts/Makefile alone and let rename microsoft and monotype to webfonts. I think I am going to modify webfonts to use mkfontscale and mkfontdir since it comes with xorg and remove the rename part. Then contact to the maintainer with patch. Hmm, the first (font vendor) part is not arbitrary - I think mkfontdir read the fonts themselves to work out the vendor part - 'webfont' is most certainly not consistent with what the font file itself says. ___ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
If none of those fonts generates a crash, I have to presume that either the X server is not using freetype 2.1.0 for its freetype font loading module or an X font server is in use. Does the directory with that fonts.dir file show up in: xset q and is X's .../modules/fonts/libfreetype.so linked against freetype 2.1.0? (It may be a dynamic link w/ the dlloader, but I presume would have to be a static link using the older elf loader.) I was seeing crashes many months ago and stopped using scalable server-side fonts as a result. I found that I didn't need any given that most of the apps I run now use Xft. At that stage I had a cvs version of freetype installed in /usr/lib. Xorg must have been linking against that rather than the version in the xorg tarfile. That is likely distribution-specific behavior, though. -JimC ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
James Cloos wrote: Mozilla uses client-side fonts via libXft. The crash in question is in the X server's freetype module which supports server-side fonts. You'll need to use an app which uses the (older) server-side font support to trigger the bug. An easy choice is xfd(1x) with a -fn option. Eg: xfd -fn -adobe-courier-medium-r-normal--0-0-100-100-m-0-iso10646-1 should trigger the bug if you have the freetype module loaded and an entry in a fonts.dir file in your fontpath that points that XLFD to a scalable font. Thanks for clarifying the difference with xft (I did wonder...). In any case, I still cannot crash my X-server with "xfd -fn " Here is my truetype font fonts.dir for reference - I remember I generated it with mkfontdir. (that's all the MS web fonts, plus the arphic chinese fonts and the microsoft japanese ones). 665 andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-ascii-0 andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-ibm-cp437 andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-ibm-cp850 andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-ibm-cp852 andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-ibm-cp866 andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-iso10646-1 andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-iso8859-10 andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-iso8859-13 andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-iso8859-15 andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-iso8859-1 andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-iso8859-2 andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-iso8859-3 andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-iso8859-4 andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-iso8859-5 andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-iso8859-9 andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-koi8-e andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-koi8-ru andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-koi8-r andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-koi8-u andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-koi8-uni andalemo.ttf -monotype-andale mono-medium-r-normal--0-0-0-0-c-0-microsoft-cp1252 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-ascii-0 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-ibm-cp437 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-ibm-cp850 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-ibm-cp852 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-ibm-cp866 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-iso10646-1 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-iso8859-10 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-iso8859-13 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-iso8859-15 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-iso8859-1 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-iso8859-2 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-iso8859-3 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-iso8859-4 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-iso8859-5 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-iso8859-8 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-iso8859-9 arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-koi8-e arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-koi8-r arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-koi8-ru arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-koi8-uni arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-koi8-u arial.ttf -monotype-arial-medium-r-normal--0-0-0-0-p-0-microsoft-cp1252 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-ascii-0 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-ibm-cp437 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-ibm-cp850 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-ibm-cp852 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-ibm-cp866 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-iso10646-1 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-iso8859-1 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-iso8859-10 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-iso8859-13 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-iso8859-15 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-iso8859-2 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-iso8859-3 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-iso8859-4 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-iso8859-5 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-iso8859-8 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-iso8859-9 arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-koi8-e arialbd.ttf -monotype-arial-bold-r-normal--0-0-0-0-p-0-koi8-
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
"Jeremy Messenger" <[EMAIL PROTECTED]> さんは書きました: > The old freetype2 do accept the rename but not now in > freetype2 2.1.10. > > no-crash: Run those.. > # cd /usr/X11R6/lib/X11/fonts/webfonts > # rm fonts.* > # mkfontscale > # mkfontdir > # fc-cache -f -v > > crash:Same way above, but rename all microsoft and monotype to > webfonts. I don't think it has anything to do with renaming. Although I *do* use "mkfontscale", "mkfontdir", and "fc-cache" as you write above, I still see the crash on SuSE Linux 9.3. And not only with the webfonts, with *many* other fonts as well. Actually I can find only very few fonts where it doesn't crash. But that may be just an accident. -- Mike FABIAN <[EMAIL PROTECTED]> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。 ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
Everything is quite normal on my system (no crashes...). James Cloos wrote: If none of those fonts generates a crash, I have to presume that either the X server is not using freetype 2.1.0 for its freetype font loading module or an X font server is in use. No, don't have a font server. From my /var/log/Xorg.0.log (II) LoadModule: "freetype" (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.so (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project" compiled for 6.8.2, module version = 2.1.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font FreeType Does the directory with that fonts.dir file show up in: xset q Font Path: /usr/local/share/fonts/truetype/,... and is X's .../modules/fonts/libfreetype.so linked against freetype 2.1.0? (It may be a dynamic link w/ the dlloader, but I presume would have to be a static link using the older elf loader.) ldd /usr/X11R6/lib/modules/fonts/libfreetype.so ldd: warning: you do not have execution permission for `/usr/X11R6/lib/modules/fonts/libfreetype.so' libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x40016000) libc.so.6 => /lib/libc.so.6 (0x40081000) libz.so.1 => /usr/lib/libz.so.1 (0x4019f000) /lib/ld-linux.so.2 (0x8000) ls -l /usr/lib/libfreetype.so.6 lrwxrwxrwx 1 root root 20 Mar 29 07:37 /usr/lib/libfreetype.so.6 -> libfreetype.so.6.3.8 (6.3.8 is 2.1.10 - 6.3.7 is 2.1.9). I was seeing crashes many months ago and stopped using scalable server-side fonts as a result. I found that I didn't need any given that most of the apps I run now use Xft. At that stage I had a cvs version of freetype installed in /usr/lib. Xorg must have been linking against that rather than the version in the xorg tarfile. That is likely distribution-specific behavior, though. -JimC ___ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
Then I am out of ideas. I'll have to give it anohter test on my box to see whether I still get the crashes. I have to upgrade from 99.14 to 99.15 anyway -JimC ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
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. FWIW. -JimC ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
> 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. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
> > > 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 ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
> "Werner" == Werner LEMBERG <[EMAIL PROTECTED]> writes: Werner> The other problem (reported by James) could be a different Werner> bug, probably in the cmap code of FreeType, and for his Werner> particular problem I would like to see a backtrace. I wasn't reporting the bug, just following up on previous notes that it manifests for some fonts but not others, and for some people but not others. My results suggest that those who saw the crash used 16bit encodings and those who did not used 8 bit encodings. But that presumption could be wrong and it could be an unlreated bug. (I have to admit I was rather a bit exhausted and didn't think of the latter when I posted the results :-/ ) -JimC -- James H. Cloos, Jr. <[EMAIL PROTECTED]> ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
James Cloos wrote: 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. Hmm, I did try the "xfd -fn ..." route with a few of the MS fonts at -iso10646-1 encoding. (I reckon there is no point trying the iso8859-X ones, as since they are so common, if there is any problem if would be "head-line news"), and I couldn't crash my X server. And I did try the arphic fonts at big5 encoding (well, my favourite), can't get it to crash either. ___ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
On Sun, 2005-07-24 at 20:37 +0200, Werner LEMBERG wrote: > > 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. Here is the link again: http://people.freebsd.org/~mezz/gdb/gdb-freetype2.txt Joe > > > Werner > -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
On Sun, 2005-07-24 at 21:43 +0200, Werner LEMBERG wrote: > > > > 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. Cool. Yeah, that's exactly what it looks like. Apparently, keithp is also on vacation, and may have a way of fixing this in xorg when he gets back. > > 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. Ah, gotcha. Joe > > > Werner > -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
For me xorg 6.8.2 crashes with freetype-2.1.10 when I try to run xterm -font "-monotype-courier new-medium-r-normal--20-0-0-0-m-0-koi8-r" On Monday 25 July 2005 03:07, James Cloos wrote: > 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. -- Andrey V. Panov http://canopus.iacp.dvo.ru/~panov/ ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
Andrey V. Panov wrote: For me xorg 6.8.2 crashes with freetype-2.1.10 when I try to run xterm -font "-monotype-courier new-medium-r-normal--20-0-0-0-m-0-koi8-r" Yes, I can finally(?) crash my x-server with this as well. On Monday 25 July 2005 03:07, James Cloos wrote: 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. ___ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
> > For me xorg 6.8.2 crashes with freetype-2.1.10 when I try to run > > xterm -font "-monotype-courier > > new-medium-r-normal--20-0-0-0-m-0-koi8-r" > > Yes, I can finally(?) crash my x-server with this as well. Can you produce a backtrace? Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
Werner LEMBERG wrote: For me xorg 6.8.2 crashes with freetype-2.1.10 when I try to run xterm -font "-monotype-courier new-medium-r-normal--20-0-0-0-m-0-koi8-r" Yes, I can finally(?) crash my x-server with this as well. Can you produce a backtrace? Here is the backtrace. It looks the same as the initial report though. My main X server binary, etc is striped, but on the other hand, I have a "proper" core dump, and I'll hang on to the 10MB file, so if you can tell me what else may be useful from the core dump, I can try getting it for you. (gdb) bt #0 0x40089ef1 in kill () from /lib/libc.so.6 #1 0x40089b15 in raise () from /lib/libc.so.6 #2 0x4008b3fd in abort () from /lib/libc.so.6 #3 0x08070f0c in ddxGiveUp () #4 0x080ea127 in AbortServer () #5 0x080ea3cf in FatalError () #6 0x080878b0 in xf86SigHandler () #7 #8 0x in ?? () #9 0x401a9f66 in FT_Do_SBit_Metrics () from /usr/X11R6/lib/modules/fonts/libfreetype.so #10 0x401aafc0 in FreeTypeRasteriseGlyph () from /usr/X11R6/lib/modules/fonts/libfreetype.so #11 0x401a9623 in FreeTypeInstanceGetGlyph () from /usr/X11R6/lib/modules/fonts/libfreetype.so #12 0x401af03f in FreeTypeLoadXFont () from /usr/X11R6/lib/modules/fonts/libfreetype.so #13 0x401b00db in FreeTypeOpenScalable () from /usr/X11R6/lib/modules/fonts/libfreetype.so #14 0x080f6bba in FontFileOpenFont () #15 0x080de5d9 in FontWakeup () #16 0x080de9ad in OpenFont () #17 0x080be89d in ProcOpenFont () #18 0x080bd122 in Dispatch () #19 0x080d02b1 in main () (gdb) ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
> Here is the backtrace. It looks the same as the initial report > though. Thanks. This assures that it is the same bug, and not a different one. I think that David Turner is back from vacation soon, and hopefully Keith Packard too. Let's wait what they have to say. I'm still heavily involved in updating my CJK package for TeXLive, so don't expect any further actions right now. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
Werner LEMBERG wrote: Here is the backtrace. It looks the same as the initial report though. Thanks. This assures that it is the same bug, and not a different one. I think that David Turner is back from vacation soon, and hopefully Keith Packard too. Let's wait what they have to say. I'm still heavily involved in updating my CJK package for TeXLive, so don't expect any further actions right now. The "sbit" part remains me of the earlier two-line patch which adds back two function pointers which David Turner removed between 2.1.9 and 2.1.10. Then the call stack going funny - most probably FT_Do_SBit_Metrics () in /usr/X11R6/lib/modules/fonts/libfreetype.so is trying to call one of those two function pointers. The main question is why David did it and/or what is the recommended change in Xorg. #7 #8 0x in ?? () #9 0x401a9f66 in FT_Do_SBit_Metrics () from /usr/X11R6/lib/modules/fonts/libfreetype.so ___ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
On Wed, Aug 03, 2005 at 08:39:06AM +0100, Hin-Tak Leung wrote: > Werner LEMBERG wrote: > The "sbit" part remains me of the earlier two-line patch which adds > back two function pointers which David Turner removed between 2.1.9 and > 2.1.10. Then the call stack going funny - most probably > FT_Do_SBit_Metrics () in /usr/X11R6/lib/modules/fonts/libfreetype.so > is trying to call one of those two function pointers. The main question > is why David did it and/or what is the recommended change in Xorg. The freetype module of Xorg tries to get accurate glyph metrics without loading the glyph. To achieve this, it uses some internal function calls (checking if the sbit metrics is available and looking at the hmtx table). If both failed, it loads the glyph at last. This behavior is chosen because it wants to avoid loading the same glyph twice (in XTextExtents and in XDrawString), if possible. A better way would be caching the glyphs loaded. Then it can simply load the glyphs to get the metrics when user wants them. Later, when the glyph is to be drawn, it can read the glyph directly from the cache. This way no freetype's internal calls are needed and the same glyph would never have to be loaded twice. (The implementation can be made easy by employing the cache subsystem of freetype.) -- Regards, olv ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
Chia I Wu wrote: On Wed, Aug 03, 2005 at 08:39:06AM +0100, Hin-Tak Leung wrote: Werner LEMBERG wrote: The "sbit" part remains me of the earlier two-line patch which adds back two function pointers which David Turner removed between 2.1.9 and 2.1.10. Then the call stack going funny - most probably FT_Do_SBit_Metrics () in /usr/X11R6/lib/modules/fonts/libfreetype.so is trying to call one of those two function pointers. The main question is why David did it and/or what is the recommended change in Xorg. The freetype module of Xorg tries to get accurate glyph metrics without loading the glyph. To achieve this, it uses some internal function calls (checking if the sbit metrics is available and looking at the hmtx table). If both failed, it loads the glyph at last. This behavior is chosen because it wants to avoid loading the same glyph twice (in XTextExtents and in XDrawString), if possible. A better way would be caching the glyphs loaded. Then it can simply load the glyphs to get the metrics when user wants them. Later, when the glyph is to be drawn, it can read the glyph directly from the cache. This way no freetype's internal calls are needed and the same glyph would never have to be loaded twice. (The implementation can be made easy by employing the cache subsystem of freetype.) Hmm, this is the way to go long term (probably why David removed the routines), and in practice, since Xorg comes with freetype, it is probably fine as long as the version of Xorg that will ship with freetype 2.1.10 is to be released with the cache mechanism. But it is going to be a problem for anybody trying to do mix-and-match. (and Xorg would need to keep the existing old code when it gets the new caching mechanism, and freetype needs to keep the old API for old Xorgs.). ___ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
On Wed, 3 Aug 2005, Chia I Wu wrote: would never have to be loaded twice. (The implementation can be made easy by employing the cache subsystem of freetype.) Cache subsystem in Freetype is Beta and cache API can change anytime... _ _ _ _ _ | |_| |\ | S L U P S K I [EMAIL PROTECTED] |_| | | | \| http://juljas.net/ ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
RE: [ft-devel] Re: xorg crashes with freetype2-2.1.10
Hello everyone, I'm back from vacation and have some hints regarding this infamous crash. - First of all, the reason why some pointers have been set to NULL in the latest package is really that: * the functions were _not_ used by the rest of the library, nor exposed through a public API. And I couldn't reasonnably guess what the X.org code was doing * the functions are completely removed in the heap-optimized version of the library. If you want to correct it safely, line 370 of 'src/sfnt/sfdriver.c' should read instead: #ifdef FT_OPTIMIZE_MEMORY 0 /* tt_find_sbit_image */, 0 /* tt_load_sbit_metrics */, #else tt_find_sbit_image, tt_load_sbit_metrics, #endif - The real problem is that the X.org code relies on features that are internal to the library. This is ok as long as its sources are embedded within the X Server (or X Font Server), but breaks when trying to rely on the library installed on the system. There aren't that many solutions, but they do exist: A/ Forget about the "optimization", load the glyphs twice and be done with it. B/ Keep a copy of the FreeType sources within X.org, and never use the system-installed version of the library. C/ Ask for a dedicated public API for the problem, which will appear in a later release of the library (e.g. 2.2.0). Do some twisted magic at compile-time: - if the version of FreeType headers used at compile time are < 2.2.0, forget about the optimization This is the only way to generate correct code that will never break in the future. By the way, I don't think I'll be able to produce a patch for X.org in the coming weeks !! Hope this helps, - David Turner - The FreeType Project (www.freetype.org) > -Message d'origine- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > la part de > Werner LEMBERG > Envoyé : dimanche 24 juillet 2005 21:44 > À : [EMAIL PROTECTED] > Cc : [EMAIL PROTECTED]; [EMAIL PROTECTED]; > freetype-devel@nongnu.org > Objet : Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10 > > > > > > > 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 > > > ___ > Freetype-devel mailing list > Freetype-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/freetype-devel > ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
> If you want to correct it safely, line 370 of > 'src/sfnt/sfdriver.c' should read instead: > > #ifdef FT_OPTIMIZE_MEMORY > 0 /* tt_find_sbit_image */, > 0 /* tt_load_sbit_metrics */, > #else > tt_find_sbit_image, > tt_load_sbit_metrics, > #endif I'll do that as a temporary fix. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Re: xorg crashes with freetype2-2.1.10
On Wed, 03 Aug 2005 12:59:07 -0500, Werner LEMBERG <[EMAIL PROTECTED]> wrote: If you want to correct it safely, line 370 of 'src/sfnt/sfdriver.c' should read instead: #ifdef FT_OPTIMIZE_MEMORY 0 /* tt_find_sbit_image */, 0 /* tt_load_sbit_metrics */, #else tt_find_sbit_image, tt_load_sbit_metrics, #endif I'll do that as a temporary fix. Thanks, it fixed my crash problem. marcus has committed in FreeBSD ports tree like this patch. Cheers, Mezz Werner -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel