Re: [ft] Segfault in FT_Get_Name_Index, Solaris 9, FreeType 2.1.8+

2006-05-24 Thread Jan-Åke Larsson
Jan-Åke Larsson wrote: Update: Just tried compiling the library with SUN cc (Workshop 11). I no longer get a segfault when linking my program to ft 2.1.8. Scratch that. It works with gcc too. Today. Perhaps it is the phase of the Moon or something, I give up. /JÅ -- The box said Windows 95

[Fwd: Re: [ft] Segfault in FT_Get_Name_Index, Sola...]

2006-05-22 Thread Jan-Åke Larsson
I'd suggest you remove this individual from the freetype list. Obviously, he doesn't want mail from it. /JÅ Original Message Subject: Re: [ft] Segfault in FT_Get_Name_Index, Sola... Date: Mon, 22 May 2006 15:38:40 +0200 (MEST) From: [EMAIL PROTECTED], Thibault Jamme@mai.liu.se

Re: [ft] In freetype how can one set font size in pt, but keep resolution independent?

2006-05-18 Thread Jan-Åke Larsson
Werner LEMBERG wrote: Well, the very problem is that neither TrueType nor PS fonts have the concept of a `design size'. This is something from the TeX world. Correct. In the TeX world, a font designed for 5pt output is visibly different from the same font as designed for 10pt. For instance

[ft] Segfault in FT_Get_Name_Index, Solaris 9, FreeType 2.1.8+

2006-05-17 Thread Jan-Åke Larsson
I get a segfault (or bus error, sometimes) from FT_Get_Name_Index on Solaris 9, with FreeType 2.1.8, 2.1.9 and 2.2.1. FreeType 2.1.7 works fine (but there, FT_LOAD_TARGET_LIGHT does not work) Steps to reproduce: Load font, map char name d to char index. Sometimes the map returns index 0,

Re: [ft] Segfault in FT_Get_Name_Index, Solaris 9, FreeType 2.1.8+

2006-05-17 Thread Jan-Åke Larsson
David Turner wrote: I don't have a Solaris 9 machine here, and won't be able to due much here. Given the line were the segfault is detected, I suppose that the value of the 'service' variable is bogus (and not NULL). Yes, but might be overwritten somewhere else, no? I don't suppose that the

Re: [ft] Segfault in FT_Get_Name_Index, Solaris 9, FreeType 2.1.8+

2006-05-17 Thread Jan-Åke Larsson
Ian Brown wrote: On the SPARC architecture, you can only access 16 bit values on 16 bit address boundaries, 32 bit values on 32 bit address boundaries etc. Yep: But dereferencing a bogus pointer would sometimes cause a bus error, sometimes a segfault, I'd imagine. /JÅ -- ceci n'est pas une