all devices regression report - 2017-11-23-10:59:07 - adfedfa4de0457ecacf5814d4a315fcaee00561d

Differences in all devices errors using gs/examples files

Previous Revision: 3ad236df1e509d0326a1fa31c98e068b5712fd75
 Current Revision: adfedfa4de0457ecacf5814d4a315fcaee00561d

commit adfedfa4de0457ecacf5814d4a315fcaee00561d
Author:     Ken Sharp <[email protected]>
AuthorDate: Thu Nov 23 17:00:06 2017 +0000
CommitDate: Thu Nov 23 17:00:28 2017 +0000

    OpenType fonts - regard fonts with multiple GSUB tables as invalid
    
    Bug #697627 "IO in gs_notify_all function"
    
    The bug title is a misnomer; the actual problem is that we have a badly
    corrupted font which appears to have 2 GSUB tables. This causes us to
    allocate two chunks of memory to hold the tables, losing the original
    reference when we allocate the second, and also to register the font
    to have the GSUB table released twice.
    
    Trying to release the same memory twice leads to us trying to access
    invalid memory, and therefore to a seg fault.
    
    So if we find we have a GSUB, and we've already allocated memory for a
    GSUB table, just throw an error.
    
    Chris thinks it may be possible to legally have multiple GSUB tables, if
    we ever find such a thing we'll have to rethink this.

base/gstype42.c

new errors:

errors that went away:

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