all devices regression report - 2017-11-16-06:31:10 - b76dc2d704fcc00edc8c1fd8ae19d01a36e22c49

Differences in all devices errors using gs/examples files

Previous Revision: 01ce294445f7988f51f63108d53a89df003f2b1e
 Current Revision: b76dc2d704fcc00edc8c1fd8ae19d01a36e22c49

commit b76dc2d704fcc00edc8c1fd8ae19d01a36e22c49
Author:     Ken Sharp <[email protected]>
AuthorDate: Thu Nov 16 13:38:59 2017 +0000
CommitDate: Thu Nov 16 13:38:59 2017 +0000

    ps2write - fix string splitting for output formatting
    
    Bug #698708 "Ghostscript loops"
    
    When writing output for ps2write, we limit the output width to 255
    characters. If a string is longer than that we try to split it on
    PostScript tokens. If we can't do that then we just break at 255
    characters and stick in a newline.
    
    The logic in here however was flawed however, it failed to update the
    pointer 'p' which points to the character currently being processed
    and did not reset the width count to 0 when the string was output.
    
    This could lead to us in an infinite loop.

devices/vector/gdevpdfu.c

new errors:

errors that went away:

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