all devices regression report - 2017-11-08-03:37:30 - e1aead165e05e98ae765d6569f39ced839d4298e
| Newsgroups | gmane.comp.printing.ghostscript.regression |
|---|---|
| Message-ID | <20171108113730.ABBFB20401B2@i7> |
Differences in all devices errors using gs/examples files Previous Revision: 1fb022758a35502b8e299248dd37207c1abc3ffe Current Revision: e1aead165e05e98ae765d6569f39ced839d4298e commit e1aead165e05e98ae765d6569f39ced839d4298e Author: Ken Sharp <[email protected]> AuthorDate: Wed Nov 8 10:04:03 2017 +0000 CommitDate: Wed Nov 8 10:04:03 2017 +0000 Guard against divide-by-zero exceptions in the halftone code Bug #697663 "FPE in gx_compute_cell_values()" Bug #698332 "FPE (Division by zero) in pick_cell_size()" These have the same root cause, in pick_cell_size() we can end up with halftone cell parameters which are (I think) improperly initialised. Certainly its possible to get to the point where we divide using one of the parameters, and if its 0 we get an error. I suspect that the halftone may be badly broken even when its not 0, but both these files are the result of fuzzing, so I doubt its possible to have a real working file get to this point. Guard against the divide-by-zero errors by checking that both the parameters are non-zero (its permissible for one to be 0 I believe) base/gshtscr.c new errors: errors that went away: errors that are not whitelisted: === ghostpdl/examples/transparency_example.ps === cp50 === === ghostpdl/examples/transparency_example.ps === psdrgb ===