[gs-bugs] [Bug 689839] PDF interpretation fails with error

[bugs.ghostscript.com-bugzilla-daemon at ghostscript.com]

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





------- Additional Comments From marcos.woehrmann at artifex.com  2008-05-13 08:45 -------
I can duplicate the problem with gshead (r8726) and gs8.62 using the command line:

  bin/gs -sDEVICE=ppmraw -o test.ppm ./failing_form.pdf

Here's the relevant PDFDEBUG output:

%Resolving: [4827 0]
<<
/F 69 /Contents ([HP-POD-PRINTINFO-START]<?xml version="1.0" encoding="UTF-8"?
>\r\n<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.hp.com/fas/PrintAPI PrintAPI.xsd" xmlns="...) /Type /Annot /Rect [
0.0 0.0 0.0 0.0 ]
/BS <<
/W 0 >>
/NM (PrintInfoAnnot) /Subtype /HWEP_DLDAnnot /T (DPPPrintInfo) /AP <<
/N 0 >>
/DA ([0] G [0 0 0] rg 0 Tc 0 Tw 100 Tz 0 TL 0 Ts 0 Tr /FdtFont 8 Tf) /HWEP_DT /printinfo >>
endobj
Error: /typecheck in --run--
Operand stack:
   --nostringval--   --dict:8/8(L)--   --dict:48/48(ro)(L)--   --nostringval--   PageSpotColors   --
dict:0/0(L)--   --dict:1/4(L)--   0   Resources
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   -
-nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   1905   1   3   
%oparray_pop   1904   1   3   %oparray_pop   1888   1   3   %oparray_pop   --nostringval--   --
nostringval--   2   1   2   --nostringval--   %for_pos_int_continue   --nostringval--   --nostringval--   -
-nostringval--   --nostringval--   --nostringval--   --nostringval--   %array_continue   --
nostringval--   %loop_continue   --nostringval--   --nostringval--
Dictionary stack:
   --dict:1149/1684(ro)(G)--   --dict:1/20(G)--   --dict:75/200(L)--   --dict:75/200(L)--   --
dict:107/127(ro)(G)--   --dict:274/300(ro)(G)--   --dict:21/25(L)--   --dict:3/5(L)--
Current allocation mode is local
GPL Ghostscript SVN PRE-RELEASE 8.63: Unrecoverable error, exit code 1





------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.