Your message dated Fri, 19 Oct 2018 05:09:47 +0200 with message-id <20181019030947.GA11270@eldamar.local> and subject line Re: Bug#909929: Regression: Error: /nocurrentpoint in --currentpoint-- has caused the Debian Bug report #909929, regarding Regression: Error: /nocurrentpoint in --currentpoint-- to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 909929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909929 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: Regression: Error: /nocurrentpoint in --currentpoint--
- From: Salvatore Bonaccorso <carnil@debian.org>
- Date: Sun, 30 Sep 2018 08:42:43 +0200
- Message-id: <153828976358.31553.17503871291460454289.reportbug@eldamar.local>
Source: ghostscript Version: 9.20~dfsg-3.2+deb9u5 Severity: important Tags: upstream Control: found -1 9.25~dfsg-1~exp1 Control: found -1 9.25~dfsg-1 Control: affects -1 + security.debian.org Control: affects -1 + release.debian.org A user reported a further regression with ghostscript after the last round of security-fixes, reported upstream as [1]. With the second.eps[2], ghostscript regresses as: > $ ./bin/gs -q -dSAFER -sDEVICE=nullpage -sOutputFile=/dev/null -dNOPAUSE ~/second.eps -c quit > Error: /nocurrentpoint in --currentpoint-- > Operand stack: > > Execution stack: > %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 2015 1 3 %oparray_pop 2014 1 3 %oparray_pop --nostringval-- 1998 1 3 %oparray_pop 1884 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- > Dictionary stack: > --dict:966/1684(ro)(G)-- --dict:0/20(G)-- --dict:82/200(L)-- --dict:12/20(L)-- > Current allocation mode is local > Last OS error: No such file or directory > Current file position is 774 > GPL Ghostscript GIT PRERELEASE 9.25: Unrecoverable error, exit code 1 The issue is present upstream (as well in master), and bisect shows that it can be tracked down to upstream commit fb713b3818b52d8a6cf62c951eba2e1795ff9624 to address CVE-2018-17183. (details in reported upstream bug). Regards, Salvatore [1] https://bugs.ghostscript.com/show_bug.cgi?id=699832 [2] https://bugs.ghostscript.com/attachment.cgi?id=15708Attachment: second.eps
Description: PostScript document
--- End Message ---
--- Begin Message ---
- To: 909929-done@bugs.debian.org
- Subject: Re: Bug#909929: Regression: Error: /nocurrentpoint in --currentpoint--
- From: Salvatore Bonaccorso <carnil@debian.org>
- Date: Fri, 19 Oct 2018 05:09:47 +0200
- Message-id: <20181019030947.GA11270@eldamar.local>
- In-reply-to: <153828976358.31553.17503871291460454289.reportbug@eldamar.local>
- References: <153828976358.31553.17503871291460454289.reportbug@eldamar.local>
Source: ghostscript Source-Version: 9.25~dfsg-3 This was fixed upstream with http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=1778db6bc10 and included in 9.25~dfsg-3 .
--- End Message ---