GNOME Bugzilla – Bug 464196
crash in Document Viewer: $ evince ~/foo/bar.pdf
Last modified: 2007-08-07 16:37:12 UTC
Version: 0.8.3 What were you doing when the application crashed? $ evince ~/foo/bar.pdf Distribution: Unknown Gnome Release: 2.18.3 2007-07-21 (FreeBSD GNOME Project) BugBuddy Version: 2.18.1 System: FreeBSD 6.2-STABLE FreeBSD 6.2-STABLE #0: Tue Jul 24 15:08:11 ADT 2007 root@dan.is:/usr/obj/usr/src/sys/GENERIC i386 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Simple Icon Theme: gnome Memory status: size: 25388 vsize: 25388 resident: 16220 share: 23354342 rss: 16220 rss_rlim: 4055 CPU usage: start_time: 0 rtime: 128 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 128 Backtrace was generated from '/usr/local/bin/evince' (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)...(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)...[New Thread 0x8131200 (runnable)] [New Thread 0x8131000 (LWP 100133)] [New Thread 0x80e5000 (sleeping)] [New LWP 100127] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Switching to LWP 100127] 0x2918d4f7 in pthread_testcancel () from /lib/libpthread.so.2
+ Trace 153350
Thread 4 (LWP 100127)
Thread 3 (Thread 0x80e5000 (sleeping))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
*** Bug 464197 has been marked as a duplicate of this bug. ***
Created attachment 93219 [details] gdb backtrace
Hope this helps
Thank you for the better stacktrace. From this we can say it's a crash in Popler, a program which evince uses to read PDFs. I've now copied this bug over to Popler's Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=11887 Would it be possible for you to attach the PDF which you use to get this crash to the Popler Bugzilla?