all devices regression report - 2018-01-26-08:16:18 - 2b155ebd780b5737aac4e8096c8fbaa5cb78212c

Differences in all devices errors using gs/examples files

Previous Revision: b82848bc26f47b5b5727d24f03d08eb3679c7243
 Current Revision: 2b155ebd780b5737aac4e8096c8fbaa5cb78212c

commit 2b155ebd780b5737aac4e8096c8fbaa5cb78212c
Author:     Chris Liddell <[email protected]>
AuthorDate: Fri Jan 19 14:28:46 2018 +0000
CommitDate: Fri Jan 26 15:02:05 2018 +0000

    Bug 694260: FAPI: tidy up error return for broken TT glyph
    
    In the event of an error retrieving a TTF glyph, we were storing the negative
    error code in the same variable we use to store the glyph length for a valid
    glyph, which is an unsigned variable, causing a valgrind error, and potential
    security issue reading uninitialized memory.
    
    In fact, other consumers silently cope with this type of problem and
    (presumably) use a notdef glyph instead. So this tweaks the error codes to
    do the same.
    
    Because we now have to differentiate between different types of error, we
    can no longer just use a negative value, so there is an enumerated type for
    the error values.

base/fapi_ft.c
base/gxfapi.h
psi/zfapi.c

new errors:

errors that went away:

errors that are not whitelisted:
=== ghostpdl/examples/transparency_example.ps === cp50 ===