Bug 695063 - "Error: /unregistered in --run--" with --saved-pages-test
Summary: "Error: /unregistered in --run--" with --saved-pages-test
Status: RESOLVED WORKSFORME
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: General (show other bugs)
Version: master
Hardware: PC Linux
: P4 normal
Assignee: Ray Johnston
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-21 14:31 UTC by Marcos H. Woehrmann
Modified: 2021-10-11 08:38 UTC (History)
1 user (show)

See Also:
Customer:
Word Size: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcos H. Woehrmann 2014-02-21 14:31:37 UTC
The following command generates an "Error: /unregistered in --run--" error:

  bin/gs -o test.pbm -sDEVICE=pbmraw --saved-pages-test ./Bug693365.pdf
Comment 1 Ray Johnston 2014-02-26 09:32:24 UTC
This is not just a saved-pages-test problem but also occurs in clist mode. It
is seen with --saved-pages-test because that forces clist mode.

I am seeing that a pattern with transparency (id == 0x25b) is calling the
gx_default_strip_tile_rectangle from gx_dc_pattern_fill_rectangle with the
bits->data == NULL, and de-referencing rwidth and rheight which are not
initialized. On linux these are 0 causing the 'unregistered' error. On Windows
I see copying from garbage locations.

Changing to use the gx_dc_pattern_trans procs by calling
gx_set_pattern_procs_trans in pdf14_clist_begin_typed_image doesn't really
help because these procs are made to write to the transparency buffers, not
to the clist.

The image_render_simple prepares the data for copy_portrait (in gxifast.c)
which call gx_dc_default_fill_masked which breaks the mask down to calls
to a rectangle which calls the (*(pdevc)->type->fill_rectangle). When the
device is a clist, this probably needs to call fill_rectangle_hl_color.
For this to work, we need some changes to support pattern hl colors since
the clist playback and pdf14_fill_rectangle_hl_color only currently allow
devn hl colors.
Comment 2 Peter Cherepanov 2020-12-28 05:11:51 UTC
Most of the files attached to the bug 693365 still fail with similar errors.
Comment 3 Ken Sharp 2021-10-11 08:38:58 UTC
I've tried the command line with all 5 files attached to bug 693365 and none of them give any errors for me.