How to debug pstoraster-Problem?

[Sven Utcke]

To follow up un my own posting:

> for pretty much any nontrivial printjob I see something like the following in the error_log:
>
> D [16/Oct/2006:22:32:43 +0200] PID 3746 (/software/cups-1.3svn-r6014/SuSE-7.3/lib/cups/filter/pstops) exited with no errors.
[...]
> D [16/Oct/2006:22:32:43 +0200] [Job 35] Last OS error: 2
> D [16/Oct/2006:22:32:43 +0200] [Job 35] ESP Ghostscript 815.03: Unrecoverable error, exit code 1
>
>
> i.e. pstoraster fails.  This is using cups-1.3svn-r6014, espgs-8.15.3, and gutenprint-5.0.0 (although I get similar results using espgs-7.05.5).  Now, the vexing thing is that running pstoraster on the _original_ PS-file does not produce an error.  In order to debug this some more I need access to the modified PS which get's passed to pstoraster --- any ideas, anyone?

Ok, I still don't know about the canonical way to debug this, but pstoraster is a script, so I could easily modify that to get a copy of the PS after pstops --- and as it turns out that (pstops) is also the culprit.  Both the pstops from 1.3svn-r6014 as well as 1.2.4 produce PostScript on which all of gs 6.51, espgs 7.05.5, and espgs 8.15.3 fail. I have, for now, replaced the pstops from 1.3svn-r6014 with the one from 1.1.17, which works for me (except for rendering the output of psnup in very low resolution).

The offending file can, for the time being, be gotten from

ftp://kogs.informatik.uni-hamburg.de/pub/utcke/misc/gewicht.ps

Any ideas?

Sven