[Groff] bug in grops (maybe)

[Gaius Mulley]

Hi,

I think a there is a bug in grops as when I try and produce a pdf file
from a ps file, gs crashes.  All sounds unconvincing, but this worked
last May (it works with cvs checkout -D 2005-05-05 groff, isn't cvs
great!) and the troff input file is trivial.

Here is the troff input file:

-------------------------------------
.LP
.PSPIC fig18.eps 3i 3i
-------------------------------------

fig18.eps is an extended postscript file (not sure if this has much effect)

fig18.eps
Description: fig18.eps

and here are the build commands

$ groff -ms t.ms > t.ps
$ gs -q -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -sOutputFile=t.pdf t.ps
Error: /invalidrestore in --restore--
Operand stack:
   --dict:1/1(L)--   --nostringval--   --nostringval--
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--
--nostringval--   2   %stopped_push--nostringval--   --nostringval--
--nostringval--   false   1   %stopped_push   1   3   %oparray_pop 1
3   %oparray_pop   1   3   %oparray_pop   1   3   %oparray_pop
.runexec2   --nostringval--   --nostringval--   --nostringval--   2
%stopped_push   --nostringval--   2   4   %oparray_pop
--nostringval--   2   4   %oparray_pop   --nostringval--
Dictionary stack:
   --dict:1120/1686(ro)(G)--   --dict:0/20(G)--   --dict:113/200(L)--
--dict:58/120(L)--
Current allocation mode is local
Last OS error: 2
Current file position is 49949
ESP Ghostscript 815.00: Unrecoverable error, exit code 1



when I checked out a groff from last May it succeeded fine, after
which I diffed the new and old postscript files and found these minor
changes:


$ diff t.ps works.ps
2,3c2,3
< %%Creator: groff version 1.19.3
< %%CreationDate: Thu Dec  8 22:56:08 2005
---
> %%Creator: groff version 1.19.2
> %%CreationDate: Thu Dec  8 22:48:52 2005
6c6
< %%+ procset grops 1.19 3
---
> %%+ procset grops 1.19 2
16c16
< %%BeginResource: procset grops 1.19 3
---
> %%BeginResource: procset grops 1.19 2
85c85
< }def
---
> }bind def
178a179
> clear

but I don't understand enough about PostScript to be sure to fix this

regards,
Gaius