| Summary: | A PDF file causes GS crash | ||
|---|---|---|---|
| Product: | Ghostscript | Reporter: | Osamu Mihara <osamu.mihara> |
| Component: | PDF Interpreter | Assignee: | Alex Cherepanov <alex> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | christinedelight.top85, michael.vrhel |
| Priority: | P4 | ||
| Version: | master | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Customer: | Word Size: | --- | |
| Attachments: | linuxkerneldevelopment.pdf | ||
|
Description
Osamu Mihara
2009-04-22 21:09:55 UTC
Created attachment 4970 [details] linuxkerneldevelopment.pdf $ gs linuxkerneldevelopment.pdf GPL Ghostscript SVN PRE-RELEASE 8.65 (2009-02-04) Copyright (C) 2009 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Processing pages 1 through 6. Page 1 >>showpage, press <return> to continue<< Page 2 Error: /unknownerror in --run-- Operand stack: --nostringval-- --dict:11/20(L)-- 471.152 736.615 Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1862 1 3 %oparray_pop 1861 1 3 %oparray_pop 1845 1 3 %oparray_pop --nostringval-- --nostringval-- 3 1 6 --nostringval-- %for_pos_int_continue --nostringval-- --nostringval-- false 1 %stopped_push --nostringval-- --nostringval-- --nostringval-- %array_continue --nostringval-- false 1 %stopped_push --nostringval-- %loop_continue --nostringval-- --nostringval-- Dictionary stack: --dict:1143/1684(ro)(G)-- --dict:1/20(G)-- --dict:75/200(L)-- --dict:75/200(L)-- --dict:106/127(ro)(G)-- --dict:280/300(ro)(G)-- --dict:22/25(L)-- --dict:4/6(L)-- --dict:22/40(L)-- --dict:1/1(ro)(G)-- --dict:9/13(L)-- Current allocation mode is local Last OS error: 11 GPL Ghostscript SVN PRE-RELEASE 8.65: Unrecoverable error, exit code 1 This bug is confirmed on the default device, x11alpha . Use -sDEVICE=x11 to work around the bug. Hi, This bug is detected during the test of PDF print workflow - So, at first time, I have seen the problem with -sDEVICE=cups. It seems that the crash depends on the params as well as devices. The following command causes crash: % gs -r300 -sDEVICE=cups -q -dBATCH -dSAFER -dQUIET -dNOPAUSE -dcupsColorSpace=3 -dcupsBitsPerColor=1 linuxkerneldevelopment.pdf But this is good: % gs -r300 -sDEVICE=cups -q -dBATCH -dSAFER -dQUIET -dNOPAUSE -dcupsColorSpace=1 -dcupsBitsPerColor=8 linuxkerneldevelopment.pdf The differences are color space and bits per color. Regards, fixed with rev 12380 |