[gs-bugs] [Bug 690587] New: setcolorspace + currentgray crashes GS
8.64
bugs.ghostscript.com-bugzilla-daemon at ghostscript.com
bugs.ghostscript.com-bugzilla-daemon at ghostscript.com
Wed Jul 1 08:15:13 PDT 2009
http://bugs.ghostscript.com/show_bug.cgi?id=690587
Summary: setcolorspace + currentgray crashes GS 8.64
Product: Ghostscript
Version: 8.64
Platform: PC
OS/Version: Windows 2000
Status: UNCONFIRMED
Severity: major
Priority: P4
Component: Regression
AssignedTo: support at artifex.com
ReportedBy: francois.robert at atex.com
QAContact: gs-bugs at ghostscript.com
The following PS program crashes GPL Ghostscript 8.64 on Win32 :
[ /Indexed /DeviceGray 0 <00> ] setcolorspace currentgray
GS 8.64 (Win32) simply dies with no error message, no mesage box.
GS 8.54 and 8.60 (Win32) returns 0.0 on the stack (as expected ? at least it
does not die...)
Note: This bug was uncovered when writing a separation procset, where
currentgray (and others) are used for probing the existence of nested
separation contexts.
FYI, another issue was uncovered during those tests :
The following incorrect program :
[ /Indexed /DeviceGray 1 <00> ] setcolorspace
on GS 8.64 produces a cryptic error message :
Error: /rangecheck in -- at 0x10081290--
On GS 8.54 and 8.60, it produces (as expected) :
Error: /rangecheck in --setcolorspace--
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the gs-bugs
mailing list