[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ft-devel] mysterious crash
From: |
Werner LEMBERG |
Subject: |
[ft-devel] mysterious crash |
Date: |
Wed, 30 May 2007 14:52:30 +0200 (CEST) |
The attached (invalid) font causes a crash on my Linux box if called
with
ftview 20 test122
gdb also shows the crash but doesn't show anything suspicious.
Interestingly, valgrind by default passes fine, but using the
--alignment=16 option yields
Invalid read of size 4
at 0x806901B: Ins_IP (ttinterp.c:6209)
by 0x806A3B5: TT_RunIns (ttinterp.c:7370)
by 0x8064445: TT_Run_Context (ttinterp.c:737)
by 0x8060826: TT_Hint_Glyph (ttgload.c:653)
by 0x8060CBA: TT_Process_Simple_Glyph (ttgload.c:770)
by 0x806184A: load_truetype_glyph (ttgload.c:1277)
by 0x806260C: TT_Load_Glyph (ttgload.c:1906)
by 0x805EC08: Load_Glyph (ttdriver.c:267)
by 0x8050D44: FT_Load_Glyph (ftobjs.c:646)
by 0x80AF534: ftc_basic_family_load_bitmap (ftcbasic.c:167)
by 0x80AEDD2: ftc_snode_load (ftcsbits.c:124)
by 0x80AF2CB: ftc_snode_compare (ftcsbits.c:375)
Address 0x457621C is not stack'd, malloc'd or (recently) free'd
However, I'm apparently too stupid to find the reason...
Can someone help, please?
Werner
test122.bz2
Description: Binary data
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [ft-devel] mysterious crash,
Werner LEMBERG <=