[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: David Turner
Subject: Re: [ft] Segfault in FT_Get_Name_Index, Solaris 9, FreeType 2.1.8+
Date: Wed, 17 May 2006 16:10:50 +0200
User-agent: Thunderbird 1.5 (Windows/20051201)


I've just tested it with FreeType CVS on a x86 Linux machine, and it seems to work well with the font you sent me. Running with valgrind doesn't show any bad memory
access or other errors.

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).

In GDB, could you dump the content of face->internal->services and send it
to me, this would be a good start.


- David

PS: By the way, does the problem happens or even changes when compiling
     with/without optimizations ?

Jan-Åke Larsson a écrit :
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, sometimes you get:
Program received signal SIGSEGV, Segmentation fault.
0xff319318 in FT_Get_Name_Index (face=0x1ed858, glyph_name=0x33548 "d")
    at /home/jalar/build/freetype-2.1.8/src/base/ftobjs.c:2378
2378          if ( service && service->name_index )

I build 2.1.7 (working) and 2.1.8 (SIGSEGV) exactly the same way:
./configure --prefix=/home/jalar; gmake (uses gcc)

Am I missing some advice for Solaris here?

Freetype mailing list

Information contained in this email message is confidential and may be 
privileged, and is intended only for use of the individual or entity named 
above. If the reader of this message is not the intended recipient, or the 
employee or agent responsible to deliver it to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited. If you have received this communication 
in error, please immediately notify the address@hidden and destroy the original 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]