Bug 105973 - use-of-uninitialized-value in SplashFTFontEngine::SplashFTFontEngine
Summary: use-of-uninitialized-value in SplashFTFontEngine::SplashFTFontEngine
Status: RESOLVED INVALID
Alias: None
Product: poppler
Classification: Unclassified
Component: splash backend (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) All
: medium minor
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-10 13:46 UTC by pdknsk
Modified: 2018-04-16 03:39 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description pdknsk 2018-04-10 13:46:12 UTC 
==17696==WARNING: MemorySanitizer: use-of-uninitialized-value
    #0 0x8e1db4 in SplashFTFontEngine::SplashFTFontEngine(bool, bool, bool, FT_LibraryRec_*) poppler/splash/SplashFTFontEngine.cc:64:23
    #1 0x8e1f36 in SplashFTFontEngine::init(bool, bool, bool) poppler/splash/SplashFTFontEngine.cc:75:14
    #2 0x79862d in SplashFontEngine::SplashFontEngine(bool, bool, bool, bool) poppler/splash/SplashFontEngine.cc:76:16
    #3 0x70e6d8 in SplashOutputDev::startDoc(PDFDoc*) poppler/poppler/SplashOutputDev.cc:1457:20
    #4 0x4bf0b1 in poppler::page_renderer::render_page(poppler::page const*, double, double, int, int, int, int, poppler::rotation_enum) const poppler/cpp/poppler-page-renderer.cpp:179:21

  Uninitialized value was created by an allocation of 'major' in the stack frame of function '_ZN18SplashFTFontEngineC2EbbbP14FT_LibraryRec_'

A harmless and unlikely bug.

(FT_Library_Version)

https://git.savannah.gnu.org/cgit/freetype/freetype2.git/tree/src/base/ftobjs.c?id=98add9e68c172e2c689a420ea3c53bd5c2772b87#n2406
Comment 1 Albert Astals Cid 2018-04-10 22:47:39 UTC 
And the pdf?
Comment 2 pdknsk 2018-04-11 13:11:47 UTC 
I've not attached any as this is with each PDF.
Comment 3 Albert Astals Cid 2018-04-12 20:17:58 UTC 
that seems actually a bug in freetype to me, i'll talk wit the freetype devels.
Comment 4 Albert Astals Cid 2018-04-12 20:21:50 UTC 
You're using an old ass freetype or what? https://git.savannah.gnu.org/cgit/freetype/freetype2.git/tree/src/base/ftobjs.c#n5186 does the right thing, .e. checking the pointer is not null, instead of checking the value of the pointer is not 0.

That was fixed in 2002, are you really using such an old version of freetype?
Comment 5 pdknsk 2018-04-16 03:39:36 UTC 
It's a recent version. I don't know how I linked to the old file. Anyway, false alarm.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.