[gs-bugs] [Bug 691527] New: PDF FTS 1.7 files Segmentation Fault
bugzilla-daemon at ghostscript.com
bugzilla-daemon at ghostscript.com
Tue Aug 3 23:58:21 UTC 2010
http://bugs.ghostscript.com/show_bug.cgi?id=691527
Summary: PDF FTS 1.7 files Segmentation Fault
Product: Ghostscript
Version: HEAD
Platform: All
OS/Version: All
Status: NEW
Severity: blocker
Priority: P4
Component: Graphics Library
AssignedTo: michael.vrhel at artifex.com
ReportedBy: ray.johnston at artifex.com
QAContact: gs-bugs at ghostscript.com
Estimated Hours: 0.0
The following files crash on my Windows 7 build with the command line:
gswin32c -Z: -r600 -sDEVICE=ppmraw -o nul: -dBandHeight=128 _____
where ____ is the file
similarly, all except fts_31_3120.pdf fail with Segmentation fault on peeves
(linux i7) with the command line:
bin/gs -Z: -r600 -sDEVICE=ppmraw -o nul: -dBandHeight=128 _____
The file list is:
fts_17_1701.pdf
fts_17_1703.pdf
fts_17_1705.pdf
fts_17_1707.pdf
fts_23_2300.pdf
fts_31_3107.pdf
fts_31_3120.pdf
I think these are all related. On Windows I looked at 3107 and was able to
get repeatable failures in device_clist_reloc_ptrs when trying to RELOC
the icc_table. There is a suspicious comment in gxclist.c:
/* Where is the GC information for the common objects that are
shared between the reader and writer. I see pointers in
there, but they don't seem to be GC. This is why I have
put the icc_table and the link cache in the reader and the
writer rather than the common. fixme: Also, if icc_cache_cl is not
included in the writer, 64bit builds will seg fault */
Thus I am assigning to Michael (apologies in advance) since it looks like
it is related to the ICC changes.
NOTE: I am available for discussion on this issue.
--
Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the gs-bugs
mailing list