Hi all,
I have removed all the memory leak errors in the gf
driver. But now when I run `ftview', it is still not loading
the glyphs. I did `valgrind ftview 20 /home/parth/cmr10
.600gf' and it is showing invalid reads in the `FTC...'
functions.
I am not able to understand the problem. Please help.
This is what I am getting:
==11084== Memcheck, a memory error detector
==11084== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==11084== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==11084== Command: ftview 20 /home/parth/cmr10.600gf
==11084==
FT_Open_Face: Requesting number of faces and named instances
FT_Stream_Open: opened `/home/parth/cmr10.600gf' (24148 bytes) successfully
TTF driver
SFNT driver
not a font using the SFNT container format
[...]
GF driver
gf_load_font: GF_ID(131) found
gf_load_font: GF_POST_POST(249) found
gf_load_font: GF Postamble found
gf_load_font: Allocated bitmap table
number of glyphs: allocated 128
FT_Open_Face: New face object, adding to list
FT_Open_Face: Creating glyph slot
FT_Open_Face: The font has 1 face
and 0 named instances for face 0
FT_Open_Face: Return 0x0
FT_Open_Face: Requesting number of faces and named instances
FT_Stream_Open: opened `/home/parth/cmr10.600gf' (24148 bytes) successfully
TTF driver
SFNT driver
not a font using the SFNT container format
[...]
GF driver
gf_load_font: GF_ID(131) found
gf_load_font: GF_POST_POST(249) found
gf_load_font: GF Postamble found
gf_load_font: Allocated bitmap table
number of glyphs: allocated 128
FT_Open_Face: New face object, adding to list
FT_Open_Face: Creating glyph slot
FT_Open_Face: The font has 1 face
and 0 named instances for face 0
FT_Open_Face: Return 0x0
FT_Open_Face: Requesting face 0
FT_Stream_Open: opened `/home/parth/cmr10.600gf' (24148 bytes) successfully
TTF driver
SFNT driver
not a font using the SFNT container format
[...]
not a BDF file
GF driver
gf_load_font: GF_ID(131) found
gf_load_font: GF_POST_POST(249) found
gf_load_font: GF Postamble found
gf_load_font: Allocated bitmap table
number of glyphs: allocated 128
FT_Open_Face: New face object, adding to list
FT_Open_Face: Creating glyph slot
FT_New_GlyphSlot: Creating new slot object
FT_New_GlyphSlot: Return 0x0
FT_Open_Face: Creating size object
FT_Open_Face: Return 0x0
FT_Open_Face: Requesting face 0
FT_Stream_Open: opened `/home/parth/cmr10.600gf' (24148 bytes) successfully
TTF driver
SFNT driver
not a font using the SFNT container format
[...]
not a BDF file
GF driver
gf_load_font: GF_ID(131) found
gf_load_font: GF_POST_POST(249) found
gf_load_font: GF Postamble found
gf_load_font: Allocated bitmap table
number of glyphs: allocated 128
FT_Open_Face: New face object, adding to list
FT_Open_Face: Creating glyph slot
FT_New_GlyphSlot: Creating new slot object
FT_New_GlyphSlot: Return 0x0
FT_Open_Face: Creating size object
FT_Open_Face: Return 0x0
==11084== Invalid read of size 1
==11084== at 0x10E758: my_face_requester (ftcommon.c:221)
==11084== by 0x4EC0836: ftc_face_node_init (ftcmanag.c:243)
==11084== by 0x4EBF8D6: FTC_MruList_New (ftcmru.c:269)
==11084== by 0x4EC1A0E: FTC_Manager_LookupFace (ftcmanag.c:325)
==11084== by 0x10F81B: FTDemo_Set_Current_Charsize (ftcommon.c:601)
==11084== by 0x10D790: event_font_change (ftview.c:1007)
==11084== by 0x10B39C: main (ftview.c:1832)
==11084== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==11084==
==11084==
==11084== Process terminating with default action of signal 11 (SIGSEGV)
==11084== Access not within mapped region at address 0x0
==11084== at 0x10E758: my_face_requester (ftcommon.c:221)
==11084== by 0x4EC0836: ftc_face_node_init (ftcmanag.c:243)
==11084== by 0x4EBF8D6: FTC_MruList_New (ftcmru.c:269)
==11084== by 0x4EC1A0E: FTC_Manager_LookupFace (ftcmanag.c:325)
==11084== by 0x10F81B: FTDemo_Set_Current_Charsize (ftcommon.c:601)
==11084== by 0x10D790: event_font_change (ftview.c:1007)
==11084== by 0x10B39C: main (ftview.c:1832)
==11084== If you believe this happened as a result of a stack
==11084== overflow in your program's main thread (unlikely but
==11084== possible), you can try to increase the size of the
==11084== main thread stack using the --main-stacksize= flag.
==11084== The main thread stack size used in this run was 8388608.
==11084==
==11084== HEAP SUMMARY:
==11084== in use at exit: 2,334,374 bytes in 653 blocks
==11084== total heap usage: 1,496 allocs, 843 frees, 3,811,806 bytes allocated
==11084==
==11084== LEAK SUMMARY:
==11084== definitely lost: 0 bytes in 0 blocks
==11084== indirectly lost: 0 bytes in 0 blocks
==11084== possibly lost: 0 bytes in 0 blocks
==11084== still reachable: 2,334,374 bytes in 653 blocks
==11084== suppressed: 0 bytes in 0 blocks
==11084== Rerun with --leak-check=full to see details of leaked memory
==11084==
==11084== For counts of detected and suppressed errors, rerun with: -v
==11084== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)