[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft-devel] Regression Crash between freetype 2.3.5 and 2.3.7
From: |
Ian Britten |
Subject: |
Re: [ft-devel] Regression Crash between freetype 2.3.5 and 2.3.7 |
Date: |
Wed, 01 Oct 2008 10:27:53 -0300 |
User-agent: |
Thunderbird 2.0.0.17 (X11/20080926) |
Werner LEMBERG wrote:
I don't know if it's the same problem, but I reported a similar
problem back at the end of July.
See my thread that ends with this post:
http://lists.gnu.org/archive/html/freetype/2008-07/msg00036.html
or the bug I filed with Mandriva
https://qa.mandriva.com/show_bug.cgi?id=42243
What about compiling with -g -O2 and running valgrind? Without -g,
valgrind reports are quite useless.
Still crashes. See attached for details.
Lemme know if you need anything more, and I'll see what I can do...
Ian
% valgrind .libs/lt-ftview 10 /usr/share/fonts/TTF/Vera.ttf
==22682== Memcheck, a memory error detector.
==22682== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==22682== Using LibVEX rev 1804, a library for dynamic binary translation.
==22682== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==22682== Using valgrind-3.3.0, a dynamic binary instrumentation framework.
==22682== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==22682== For more details, rerun with: -v
==22682==
==22682== Use of uninitialised value of size 4
==22682== at 0x40778B1: FTC_Manager_LookupFace (ftcmanag.c:327)
==22682== by 0x40778ED: ftc_basic_family_get_count (ftcbasic.c:141)
==22682== by 0x4077CE6: ftc_snode_new (ftcsbits.c:215)
==22682== by 0x4078733: FTC_Cache_NewNode (ftccache.c:454)
==22682== by 0x4078A5B: FTC_SBitCache_LookupScaler (ftcbasic.c:743)
==22682== by 0x804D0B3: FTDemo_Index_To_Bitmap (ftcommon.c:800)
==22682== by 0x804D2CD: FTDemo_Draw_Index (ftcommon.c:931)
==22682== by 0x804B039: main (ftview.c:385)
==22682==
==22682== Use of uninitialised value of size 4
==22682== at 0x40779E8: FTC_Manager_LookupSize (ftcmanag.c:201)
==22682== by 0x4077DC5: ftc_basic_family_load_bitmap (ftcbasic.c:161)
==22682== by 0x4077B1D: ftc_snode_load (ftcsbits.c:124)
==22682== by 0x4077D67: ftc_snode_new (ftcsbits.c:236)
==22682== by 0x4078733: FTC_Cache_NewNode (ftccache.c:454)
==22682== by 0x4078A5B: FTC_SBitCache_LookupScaler (ftcbasic.c:743)
==22682== by 0x804D0B3: FTDemo_Index_To_Bitmap (ftcommon.c:800)
==22682== by 0x804D2CD: FTDemo_Draw_Index (ftcommon.c:931)
==22682== by 0x804B039: main (ftview.c:385)
==22682==
==22682== Invalid read of size 4
==22682== at 0x4077DDA: ftc_basic_family_load_bitmap (ftcbasic.c:164)
==22682== by 0x4077B1D: ftc_snode_load (ftcsbits.c:124)
==22682== by 0x4077D67: ftc_snode_new (ftcsbits.c:236)
==22682== by 0x4078733: FTC_Cache_NewNode (ftccache.c:454)
==22682== by 0x4078A5B: FTC_SBitCache_LookupScaler (ftcbasic.c:743)
==22682== by 0x804D0B3: FTDemo_Index_To_Bitmap (ftcommon.c:800)
==22682== by 0x804D2CD: FTDemo_Draw_Index (ftcommon.c:931)
==22682== by 0x804B039: main (ftview.c:385)
==22682== Address 0xec835657 is not stack'd, malloc'd or (recently) free'd
==22682==
==22682== Process terminating with default action of signal 11 (SIGSEGV)
==22682== Access not within mapped region at address 0xEC835657
==22682== at 0x4077DDA: ftc_basic_family_load_bitmap (ftcbasic.c:164)
==22682== by 0x4077B1D: ftc_snode_load (ftcsbits.c:124)
==22682== by 0x4077D67: ftc_snode_new (ftcsbits.c:236)
==22682== by 0x4078733: FTC_Cache_NewNode (ftccache.c:454)
==22682== by 0x4078A5B: FTC_SBitCache_LookupScaler (ftcbasic.c:743)
==22682== by 0x804D0B3: FTDemo_Index_To_Bitmap (ftcommon.c:800)
==22682== by 0x804D2CD: FTDemo_Draw_Index (ftcommon.c:931)
==22682== by 0x804B039: main (ftview.c:385)
==22682==
==22682== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 35 from 1)
==22682== malloc/free: in use at exit: 1,502,019 bytes in 580 blocks.
==22682== malloc/free: 931 allocs, 351 frees, 1,604,047 bytes allocated.
==22682== For counts of detected errors, rerun with: -v
==22682== searching for pointers to 580 not-freed blocks.
==22682== checked 1,646,776 bytes.
==22682==
==22682== LEAK SUMMARY:
==22682== definitely lost: 0 bytes in 0 blocks.
==22682== possibly lost: 0 bytes in 0 blocks.
==22682== still reachable: 1,502,019 bytes in 580 blocks.
==22682== suppressed: 0 bytes in 0 blocks.
==22682== Rerun with --leak-check=full to see details of leaked memory.