bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: silent failure with ?out-of-memory? involving .PSPIC


From: dan
Subject: Re: silent failure with ?out-of-memory? involving .PSPIC
Date: Fri, 03 Aug 2007 15:11:08 -0400

Sir,

The previous exchange is below for reference.

I am trying to isolate a pattern, but I find that
just switching order of PSPIC-referenced external
files causes groff to produce *.PS output that breaks
both /Applications/Preview.app and `ps2pdf' (again,
groff does not in any way complain).

--dan

=============================


% ps2pdf geer.book2.PS geer.book2.PDF
Error: /rangecheck in --index--
Operand stack:
   1
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--   0   5   %oparray_pop   --nostringval--
 --nostringval--   --nostringval--
Dictionary stack:
   --dict:1046/1123(ro)(G)--   --dict:0/20(G)--   --dict:75/200(L)--
--dict:60/120(L)--   --dict:75/200(L)--
Current allocation mode is local
Last OS error: 2
Current file position is 17290844
AFPL Ghostscript 8.00: Unrecoverable error, exit code 1
make: *** [geer.book2.PDF] Error 1



=============================

Werner LEMBERG writes:
 | 
 | > When run through groff, the file with the five .PSPIC callouts only
 | > shows four of them, and from that point forward no .PSPIC is
 | > included.  If a prior one is removed experimentally, then the output
 | > gets one more .PSPIC down the line before it stops processing them.
 | > This seems prima facie to be out-of-memory, but the failure is
 | > entirely silent.
 | 
 | I've never heard of that problem, and without seeing the source I
 | can't run a debugger on this.  Please drop me something privately for
 | further investigation.  Of course, I would be glad if you could reduce
 | it as much as possible, still triggering the bug.
 | 
 | Note, however, in case that I find a bug, you have to recompile groff
 | (or pic) from the CVS.
 | 
 | 
 |     Werner




reply via email to

[Prev in Thread] Current Thread [Next in Thread]