[gs-bugs] [Bug 690497] New: jbig2dec fails to decode image
properly...
bugs.ghostscript.com-bugzilla-daemon at ghostscript.com
bugs.ghostscript.com-bugzilla-daemon at ghostscript.com
Fri May 22 13:33:19 PDT 2009
http://bugs.ghostscript.com/show_bug.cgi?id=690497
Summary: jbig2dec fails to decode image properly...
Product: jbig2dec
Version: trunk
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P4
Component: Rendering
AssignedTo: ralph.giles at artifex.com
ReportedBy: sebras at hotmail.com
QAContact: gs-bugs at ghostscript.com
Original problem appeared when running mupdf in valgrind:
==16144== Invalid read of size 1
==16144== at 0x80A495F: jbig2_set_bits (in
/home/sebras/src/mupdf2/build/linux-x86-debug/pdfdraw)
==16144== by 0x80A4D18: jbig2_decode_generic_mmr (in
/home/sebras/src/mupdf2/build/linux-x86-debug/pdfdraw)
==16144== by 0x80A0D99: jbig2_symbol_dictionary (in
/home/sebras/src/mupdf2/build/linux-x86-debug/pdfdraw)
==16144== by 0x809E601: jbig2_data_in (in
/home/sebras/src/mupdf2/build/linux-x86-debug/pdfdraw)
==16144== by 0x808B4A6: fz_processjbig2d (filt_jbig2d.c:114)
==16144== by 0x8084BC4: fz_process (stm_filter.c:19)
==16144== by 0x8086376: fz_processpipeline (filt_pipeline.c:114)
==16144== by 0x8084BC4: fz_process (stm_filter.c:19)
==16144== by 0x8085408: fz_readimp (stm_read.c:62)
==16144== by 0x8085BDB: fz_readbytex (stm_read.c:279)
==16144== by 0x8085E4B: fz_readbyte (fitz_stream.h:393)
==16144== by 0x8085EBF: fz_readall (stm_misc.c:63)
==16144== by 0x805370E: pdf_loadstream (pdf_stream.c:476)
==16144== by 0x8069168: pdf_loadimage (pdf_image.c:410)
==16144== by 0x8068F3D: pdf_loadimage (pdf_image.c:364)
==16144== by 0x8058B50: preloadxobject (pdf_resources.c:164)
==16144== by 0x8059659: pdf_loadresources (pdf_resources.c:430)
==16144== by 0x8070C21: pdf_loadxobject (pdf_xobject.c:72)
==16144== by 0x8058A73: preloadxobject (pdf_resources.c:154)
==16144== by 0x8059659: pdf_loadresources (pdf_resources.c:430)
==16144== by 0x8057577: pdf_loadpage (pdf_page.c:225)
==16144== by 0x804A06A: drawloadpage (pdfdraw.c:155)
==16144== by 0x804A1BA: drawpnm (pdfdraw.c:216)
==16144== by 0x804AD9B: drawpages (pdfdraw.c:402)
==16144== by 0x804B0EB: main (pdfdraw.c:481)
==16144== Address 0x4347857 is 0 bytes after a block of size 23 alloc'd
==16144== at 0x4021620: malloc (vg_replace_malloc.c:149)
==16144== by 0x80A585C: jbig2_image_new (in
/home/sebras/src/mupdf2/build/linux-x86-debug/pdfdraw)
==16144== by 0x80A0ADA: jbig2_symbol_dictionary (in
/home/sebras/src/mupdf2/build/linux-x86-debug/pdfdraw)
==16144== by 0x809E601: jbig2_data_in (in
/home/sebras/src/mupdf2/build/linux-x86-debug/pdfdraw)
==16144== by 0x808B4A6: fz_processjbig2d (filt_jbig2d.c:114)
==16144== by 0x8084BC4: fz_process (stm_filter.c:19)
==16144== by 0x8086376: fz_processpipeline (filt_pipeline.c:114)
==16144== by 0x8084BC4: fz_process (stm_filter.c:19)
==16144== by 0x8085408: fz_readimp (stm_read.c:62)
==16144== by 0x8085BDB: fz_readbytex (stm_read.c:279)
==16144== by 0x8085E4B: fz_readbyte (fitz_stream.h:393)
==16144== by 0x8085EBF: fz_readall (stm_misc.c:63)
==16144== by 0x805370E: pdf_loadstream (pdf_stream.c:476)
==16144== by 0x8069168: pdf_loadimage (pdf_image.c:410)
==16144== by 0x8068F3D: pdf_loadimage (pdf_image.c:364)
==16144== by 0x8058B50: preloadxobject (pdf_resources.c:164)
==16144== by 0x8059659: pdf_loadresources (pdf_resources.c:430)
==16144== by 0x8070C21: pdf_loadxobject (pdf_xobject.c:72)
==16144== by 0x8058A73: preloadxobject (pdf_resources.c:154)
==16144== by 0x8059659: pdf_loadresources (pdf_resources.c:430)
==16144== by 0x8057577: pdf_loadpage (pdf_page.c:225)
==16144== by 0x804A06A: drawloadpage (pdfdraw.c:155)
==16144== by 0x804A1BA: drawpnm (pdfdraw.c:216)
==16144== by 0x804AD9B: drawpages (pdfdraw.c:402)
==16144== by 0x804B0EB: main (pdfdraw.c:481)
jbig2 decoder FATAL ERROR: ran off the end of the entries table! (513 >= 512)
jbig2 decoder FATAL ERROR: could not construct Symbol ID huffman table! (segment
0x03)
Running jbig2dec on the extracted image gives an incorrect image.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the gs-bugs
mailing list