[cups.general] Debugging the filter chain?

[Matthias Apitz]

Johannes Meixner wrote:

> Regarding input and output data it is a bit more tricky.
> You may exchange step by step each filter binary by a
> selfmade script which writes its input into a file.

Depending on your Operating System, you may truss/strace the cupsd process
(using the -f flag to follow childs) to get an idea which of the filter
childs is causing the problem. It needs a bit understanding about UNIX sys
calls to read and understand the output, though.

HIH

        matthias