Summary: | Non-initialized variable and strange behaviour usin streams | ||
---|---|---|---|
Product: | poppler | Reporter: | Stephane Magnenat <stephane> |
Component: | general | Assignee: | poppler-bugs <poppler-bugs> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | high | ||
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Test-case for the bug described in the report
Makefile for the testcase |
Description
Stephane Magnenat
2006-08-16 01:53:00 UTC
Created attachment 6581 [details]
Test-case for the bug described in the report
Created attachment 6582 [details]
Makefile for the testcase
A stream of type strFile returns the dict you passed to it in the constructor, if that dict is "wrong" probably is your fault. Are you using a zlib enabled poppler? This can cause misbehaviour in Flate Streams. By the way that seems much more a thing to deal on the mailing list or irc than on bugzilla. (In reply to comment #3) > A stream of type strFile returns the dict you passed to it in the constructor, > if that dict is "wrong" probably is your fault. The stream in question was the basestream returned by the PDFDoc object, so I supposed allocating the stream's members was the responsability of the PDFDoc constructor, did I missed something here ? > Are you using a zlib enabled poppler? This can cause misbehaviour in Flate > Streams. I'm using ubuntu deb. ldd /usr/lib/libpoppler.so does say libz is linked in. Is there another way to know wether zlib is enabled or not ? Nevertheless I don't think my libpoppler is buggy as kpdf works fine. I just probably have missed something about the API. > By the way that seems much more a thing to deal on the mailing list or irc > than on bugzilla. Ok, I will direct further question/remarks there. Thanks Steph Is anything still required on this issue? 1.5 years and no answer to Brad, i'll take it as a "no" |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.