New Ghostscript/GhostPDL compiler warnings - 2018-09-06-23:45:07 - fb713b3818b52d8a6cf62c951eba2e1795ff9624

Previous Revision: 0d8c7d563745bfd89051a203267fcbf2492ecfcc
 Current Revision: fb713b3818b52d8a6cf62c951eba2e1795ff9624

commit fb713b3818b52d8a6cf62c951eba2e1795ff9624
Author:     Chris Liddell <[email protected]>
AuthorDate: Thu Sep 6 09:16:22 2018 +0100
CommitDate: Thu Sep 6 17:14:28 2018 +0100

    Bug 699708 (part 1): 'Hide' non-replaceable error handlers for SAFER
    
    We already had a 'private' dictionary for non-standard errors: gserrordict.
    
    This now includes all the default error handlers, the dictionary is made
    noaccess and all the prodedures are bound and executeonly.
    
    When running with -dSAFER, in the event of a Postscript error, instead of
    pulling the handler from errordict, we'll pull it from gserrordict - thus
    malicious input cannot trigger problems by the use of custom error handlers.
    
    errordict remains open and writeable, so files such as the Quality Logic tests
    that install their own handlers will still 'work', with the exception that the
    custom error handlers will not be called.
    
    This is a 'first pass', 'sledgehammer' approach: a nice addition would to allow
    an integrator to specify a list of errors that are not to be replaced (for
    example, embedded applications would probably want to ensure that VMerror is
    always handled as they intend).

Resource/Init/gs_init.ps
psi/interp.c



Ghostscript:

new cppcheck warnings (Cppcheck 1.72): 

psi/interp.c:1272: error: Uninitialized variable: htemp
psi/interp.c:1659: error: Uninitialized variable: htemp
psi/interp.c:1164: error: Expression 'iref_temp=(const struct ref_s*)iref_packed,iref_temp' depends on order of evaluation of side effects
psi/interp.c:1374: error: Expression 'iref_temp=(const struct ref_s*)iref_packed,iref_temp' depends on order of evaluation of side effects

http://miles.ghostscript.com:8080/artifex/fb713b3818b52d8a6cf62c951eba2e1795ff9624/gs-cppcheck.txt