[gs-bugs] [Bug 698067] - MuPDF - wrong startxref after incremental save with xref streams

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698067

Bug ID: 698067
Summary: wrong startxref after incremental save with xref
streams
Product: MuPDF
Version: master
Hardware: PC
OS: Windows 10
Status: UNCONFIRMED
Severity: normal
Priority: P4
Component: mupdf
Assignee: mupdf-***@artifex.com
Reporter: ***@outlook.de
QA Contact: gs-***@ghostscript.com
Word Size: ---

Created attachment 13801
--> http://bugs.ghostscript.com/attachment.cgi?id=13801&action=edit
PDF with /ObjStm

Doing incremental updates for PDFs with streamed xrefs leads to wrong startxref
values in the update part - *BUT* only for 32-bit version, 64bit version works
correctly.

Attached example:
mutool portfolio t.pdf a draft.png draft

leads to correct result with x64 version of mutool, wrong result with x86
version.

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698067

--- Comment #1 from Jorj <***@outlook.de> ---
Created attachment 13802
--> http://bugs.ghostscript.com/attachment.cgi?id=13802&action=edit
a picture (irrelevant for the case)

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698067

Ardo <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Blocks| |698375

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698067

Robin Watts <***@artifex.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
CC| |***@artifex.com

--- Comment #2 from Robin Watts <***@artifex.com> ---
Fixed as a result of:

commit f595e889b91a674eb94db7ca4d832da54f5194cd
Author: Tor Andersson <***@artifex.com>
Date: Thu Aug 17 15:01:09 2017 +0200

Use int64_t for public file API offsets.

Don't mess with conditional compilation with LARGEFILE -- always expose
64-bit file offsets in our public API.

Thanks for the report!