b***@artifex.com
2017-08-19 10:19:35 UTC
http://bugs.ghostscript.com/show_bug.cgi?id=698375
Bug ID: 698375
Summary: A possible fix for bug 697795 and 698067
Product: MuPDF
Version: master
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: P4
Component: mupdf
Assignee: mupdf-***@artifex.com
Reporter: ***@gmail.com
QA Contact: gs-***@ghostscript.com
Word Size: ---
The above referenced bugs are both caused by a wrong implicit type-cast in
source/pdf/pdf-write.c (mupdf 1.11)
This wrong type-cast is evident for Windows-32 bit, whilst is harmless for
other platforms/architectures.
The following change in pdf-write.c
from:
static void writexrefstream(fz_context *ctx, pdf_document *doc, pdf_write_state
*opts, int from, int to, int first, int main_xref_offset, int startxref)
to:
static void writexrefstream(fz_context *ctx, pdf_document *doc, pdf_write_state
*opts, int from, int to, int first, int main_xref_offset, fz_off_t startxref)
fixes the bugs. (tested on Windows 32/64, Linux 32/64, MacOS)
Bug ID: 698375
Summary: A possible fix for bug 697795 and 698067
Product: MuPDF
Version: master
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: P4
Component: mupdf
Assignee: mupdf-***@artifex.com
Reporter: ***@gmail.com
QA Contact: gs-***@ghostscript.com
Word Size: ---
The above referenced bugs are both caused by a wrong implicit type-cast in
source/pdf/pdf-write.c (mupdf 1.11)
This wrong type-cast is evident for Windows-32 bit, whilst is harmless for
other platforms/architectures.
The following change in pdf-write.c
from:
static void writexrefstream(fz_context *ctx, pdf_document *doc, pdf_write_state
*opts, int from, int to, int first, int main_xref_offset, int startxref)
to:
static void writexrefstream(fz_context *ctx, pdf_document *doc, pdf_write_state
*opts, int from, int to, int first, int main_xref_offset, fz_off_t startxref)
fixes the bugs. (tested on Windows 32/64, Linux 32/64, MacOS)
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are receiving this mail because:
You are the QA Contact for the bug.