GNOME Bugzilla – Bug 324575
crash when reloading
Last modified: 2005-12-20 08:50:00 UTC
Distribution: Fedora Core release 4 (Stentz) Package: evince Severity: major Version: GNOME2.10.0 0.4.x Gnome-Distributor: Red Hat, Inc Synopsis: crash when reloading Bugzilla-Product: evince Bugzilla-Component: general Bugzilla-Version: 0.4.x BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Steps to reproduce the crash: 1. start evince 2. reload files (PS or PDF) several times 3. then suddenly crash Expected Results: How often does this happen? Additional Information: 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) `shared object read from target memory' 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) [Thread debugging using libthread_db enabled] [New Thread -1208392000 (LWP 849)] [New Thread -1211745360 (LWP 850)] (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) 0x0056d402 in __kernel_vsyscall ()
+ Trace 64714
Thread 1 (Thread -1208392000 (LWP 849))
------- Bug created by bug-buddy at 2005-12-20 06:31 -------
Thanks for reporting. This bug should be fixed in CVS already. *** This bug has been marked as a duplicate of 314986 ***