GNOME Bugzilla – Bug 392987
crash in Document Viewer: started evince from comm...
Last modified: 2007-01-05 10:51:26 UTC
Version: 0.6.1 What were you doing when the application crashed? started evince from command line, crashed straight away. Distribution: Gentoo Base System version 1.12.8 Gnome Release: 2.16.2 2006-12-14 (Gentoo) BugBuddy Version: 2.16.0 Memory status: size: 43069440 vsize: 0 resident: 43069440 share: 0 rss: 12402688 rss_rlim: 0 CPU usage: start_time: 1167962434 rtime: 0 utime: 25 stime: 0 cutime:23 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evince' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1228072768 (LWP 1198)] [New Thread -1229333616 (LWP 1199)] 0xb7fb6410 in ?? ()
+ Trace 99497
trying to get a more useful trace :)
OK here's a better trace. It SEG faults about once every 3 or 4 times, regardless of the pdf I'm opening. I _think_ it's something to do with the thumbnails, as after bug-buddy has started, I can still look through the pdf, but there are no thumbnails. I can get around it by running: $ evince & evince a.pdf this still doesn't look complete, what else can I recompile? (gdb) run '/home/iain/Desktop/a.pdf' Starting program: /usr/bin/evince '/home/iain/Desktop/a.pdf' Failed to read a valid object file image from memory. [Thread debugging using libthread_db enabled] [New Thread -1228318528 (LWP 19927)] [New Thread -1229579376 (LWP 19928)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1228318528 (LWP 19927)] 0xb709ff6a in FcCompare () from /usr/lib/libfontconfig.so.1 (gdb) thread apply all bt
+ Trace 99504
Thread 2 (Thread -1229579376 (LWP 19928))
Thread 1 (Thread -1228318528 (LWP 19927))
Looks like another crash in fontconfig. Does it happens every time with the same pdf file? If so, could you attach such a pdf file to this bug? A longer backtrace would help too. Thanks you very much for the report. Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 374750 ***