[gs-bugs] [Bug 693054] interpreter failure with fts.0980 and fts.0982

[bugzilla-daemon at ghostscript.com]

http://bugs.ghostscript.com/show_bug.cgi?id=693054

--- Comment #7 from Hin-Tak Leung <hintak at ghostscript.com> 2012-06-08 00:38:22 UTC ---
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #3)
run
> > gx_default_strip_copy_rop() but ignore its return status and still returning
> > zero.
> 
> No, because the error code may be caused by other things, and simply ignoring
> it would be bad.

Ignoring the return status is no worse than the current situation, which is
just making up a return value (zero).

> The best answer is probably to modify the rop value used.
> 
> In your patch, try adding:
> 
>   lop = rop3_know_D_0_(lop);
> 
> before the call.
> 
> That will modify the lop to one that no longer uses 'D' (and always assumes
> it's 0). The results will not be correct in all cases, but in the absence of
> someone fixing get_bits_rectangle it'll be as good as we can do.

The *best* answer is to do rop3 optimally & natively with pxl features, and 
by-pass and "protect" gx_default_(). That still does not address its own
limitation and other drivers (pswrite & possibly others)' use of gx_default().

-- 
Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.