pdftotext crashed with SIGSEGV in TextPage::beginWord()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Poppler |
Fix Released
|
Medium
|
|||
poppler (Ubuntu) |
Fix Released
|
Medium
|
Ubuntu Desktop Bugs |
Bug Description
Crashed in the background while downloading some pdf's
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Tue Jul 29 18:34:17 2008
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/pdftotext
NonfreeKernelMo
Package: poppler-utils 0.8.4-1.1
PackageArchitec
ProcCmdline: pdftotext -enc UTF-8 -q -nopgbrk /home/username/
ProcEnviron:
PATH=/
LANG=en_AU.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: poppler
StacktraceTop:
TextPage:
TextPage::addChar () from /usr/lib/
TextOutputDev:
Gfx::go () from /usr/lib/
Gfx::display () from /usr/lib/
Title: pdftotext crashed with SIGSEGV in TextPage:
Uname: Linux 2.6.26-4-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video
Changed in poppler: | |
status: | Unknown → Confirmed |
Changed in poppler: | |
status: | Confirmed → Fix Released |
Changed in poppler: | |
importance: | Unknown → Medium |
Changed in poppler: | |
importance: | Medium → Unknown |
Changed in poppler: | |
importance: | Unknown → Medium |
Created an attachment (id=17958)
Fix bug in TextOutputDev.cc
Attaching the PDF file would assist with debugging this problem.
From the stack trace I could see one problem. At #2 the string contains only the unicode byte order marker FEFF. At this point in the code the length should be 0, not 1. Patch to fix this is attached.
Without the original PDF file I do not know if this patch will fix this bug.