GNOME Bugzilla – Bug 457604
crash in Evolution:
Last modified: 2007-08-17 09:08:41 UTC
What were you doing when the application crashed? Distribution: Mandriva Linux release 2007.0 (Official) for i586 Gnome Release: 2.16.0 2006-09-04 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.17-14mdv #1 SMP Wed May 9 21:11:43 MDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Ia Ora Free Icon Theme: gnome Memory status: size: 194314240 vsize: 194314240 resident: 32268288 share: 21704704 rss: 32268288 rss_rlim: 4294967295 CPU usage: start_time: 1184655012 rtime: 438 utime: 276 stime: 162 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/i686/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1236748576 (LWP 8345)] [New Thread -1364542560 (LWP 9347)] [New Thread -1329079392 (LWP 8594)] [New Thread -1339036768 (LWP 8593)] [New Thread -1330644064 (LWP 8591)] [New Thread -1320387680 (LWP 8588)] [New Thread -1311994976 (LWP 8587)] [New Thread -1303602272 (LWP 8563)] [New Thread -1277756512 (LWP 8561)] [New Thread -1268970592 (LWP 8560)] [New Thread -1243395168 (LWP 8558)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 148549
Thread 11 (Thread -1243395168 (LWP 8558)): #-1 0xbfffe410 in __kernel_vsyscall () No symbol table info available. Thread 10 (Thread -1268970592 (LWP 8560)): #-1 0xbfffe410 in __kernel_vsyscall () No symbol table info available. Thread 9 (Thread -1277756512 (LWP 8561)): #-1 0xbfffe410 in __kernel_vsyscall () No symbol table info available. Thread 8 (Thread -1303602272 (LWP 8563)): #-1 0xbfffe410 in __kernel_vsyscall () No symbol table info available. Thread 7 (Thread -1311994976 (LWP 8587)): #-1 0xbfffe410 in __kernel_vsyscall () No symbol table info available. Thread 6 (Thread -1320387680 (LWP 8588)): #-1 0xbfffe410 in __kernel_vsyscall () No symbol table info available. Thread 5 (Thread -1330644064 (LWP 8591)): #-1 0xbfffe410 in __kernel_vsyscall () No symbol table info available. Thread 4 (Thread -1339036768 (LWP 8593)): #-1 0xbfffe410 in __kernel_vsyscall () No symbol table info available. Thread 3 (Thread -1329079392 (LWP 8594)): #-1 0xbfffe410 in __kernel_vsyscall () No symbol table info available. Thread 2 (Thread -1364542560 (LWP 9347)): #-1 0xbfffe410 in __kernel_vsyscall () No symbol table info available. Thread 1 (Thread -1236748576 (LWP 8345)): #-1 0xbfffe410 in __kernel_vsyscall () No symbol table info available. ----------- .xsession-errors --------------------- Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded --------------------------------------------------
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 312348 ***