From 38c9ed23c3d05c6c217db287ae15c97498a69dd7 Mon Sep 17 00:00:00 2001 From: Jay Berkenbilt Date: Fri, 22 Jun 2018 10:44:08 -0400 Subject: Treat content stream parsing errors as an error, not a warning If parsing content streams is treated as a warning, there is no way for a caller to know if a parsing operation has failed. This is very dangerous and will likely result in data loss when token filters are parser callbacks are in use. --- libqpdf/QPDFObjectHandle.cc | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'libqpdf') diff --git a/libqpdf/QPDFObjectHandle.cc b/libqpdf/QPDFObjectHandle.cc index d1bc58ca..f4a8a0a4 100644 --- a/libqpdf/QPDFObjectHandle.cc +++ b/libqpdf/QPDFObjectHandle.cc @@ -1290,10 +1290,9 @@ QPDFObjectHandle::pipeContentStreams( if (! stream.pipeStreamData(p, 0, qpdf_dl_specialized)) { QTC::TC("qpdf", "QPDFObjectHandle errors in parsecontent"); - warn(stream.getOwningQPDF(), - QPDFExc(qpdf_e_damaged_pdf, "content stream", - description, 0, - "errors while decoding content stream")); + throw QPDFExc(qpdf_e_damaged_pdf, "content stream", + description, 0, + "errors while decoding content stream"); } } } -- cgit v1.2.3-54-g00ecf