IM fails on gzipped Postscript image
Posted: 2015-11-21T05:24:52-07:00
Trying to get around the nasty bug present in IM 6.7.2 (the latest version in standard CentOS 6 repositories), I installed IM 6.9.2-6 from a third-party repository Les RPM de Remi. Testing it with my scripts I got into a problem with converting/displaying gzipped Postscript images.
The same image, uncompressed manually, displays correctly. I have not seen any problem with the same image first converted to gif and then gzipped.
I wonder whether it is a real bug in IM or just some problem with the package from a third-party repository. Can anyone reproduce it?
The failure occurs on any ps.gz file I tried. Still, the first image I got into it is available as 50kB im.ps.gz
Code: Select all
>display im.ps.gz
Error: /undefined in ^Q
Operand stack:
-1.22178e+17
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 1739 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval--
Dictionary stack:
--dict:1156/1684(ro)(G)-- --dict:0/20(G)-- --dict:71/200(L)--
Current allocation mode is local
Current file position is 9
GPL Ghostscript 8.70: Unrecoverable error, exit code 1
Error: /undefined in ^Q
Operand stack:
-1.22178e+17
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 1739 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval--
Dictionary stack:
--dict:1156/1684(ro)(G)-- --dict:0/20(G)-- --dict:71/200(L)--
Current allocation mode is local
Current file position is 9
GPL Ghostscript 8.70: Unrecoverable error, exit code 1
I wonder whether it is a real bug in IM or just some problem with the package from a third-party repository. Can anyone reproduce it?
The failure occurs on any ps.gz file I tried. Still, the first image I got into it is available as 50kB im.ps.gz