GNOME Bugzilla – Bug 363994
bad parsing of math-crowded pdf; crash at closing
Last modified: 2006-11-04 20:35:26 UTC
Description of the crash: evince renders file badly, then crashes when I quit Steps to reproduce the crash: 1. I open the file, 2. see some garbage 3. and close evince Expected Results: read a long file in Hungarian about Probability Theory How often does this happen? with files from this author, each time as I try to open them http://digitus.itk.ppke.hu/~rasonyi/valszam1.pdf ...2.pdf etc these files are several years old. with the only new file on the web page of Mr Rasonyi, http://digitus.itk.ppke.hu/~rasonyi/Hf1.pdf evince has NO problems at all. Additional Information: - on my machine, last ver of gpdf shows either nothing at all or garbage; BUT! I have seen a guy viewing this very pdf in gpdf on ubuntu ((confused)) - http://pdfdl.oceighty.net/pdf2html.php?url=http://digitus.itk.ppke.hu/~rasonyi/valszam1.pdf shows almost the same garbage that evince - the pdf file seems to be originated from TeX and contains a LOT of math symbols and Hungarian accented letters - acrobat-reader 7.0.5 (for linux) renders file without problems, but when I try to copypaste from it, I get the good ol' garbage Debugging Information: Backtrace was generated from '/usr/bin/evince' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227417936 (LWP 3325)] [New Thread -1231172688 (LWP 3326)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb7ad9511 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 77547
Thread 1 (Thread -1227417936 (LWP 3325))
This looks like a Poppler or Cairo issue. Feel free to open a bug on one of these projects if you can reproduce with a better stacktrace.