GNOME Bugzilla – Bug 430571
crash in Evolution: Started the program. Thi...
Last modified: 2007-06-11 11:54:38 UTC
What were you doing when the application crashed? Started the program. Think it was fetching email... Distribution: Unknown Gnome Release: 2.18.0 2007-03-19 (Archlinux) BugBuddy Version: 2.18.1 System: Linux 2.6.20-ARCH #1 SMP PREEMPT Mon Apr 9 16:29:54 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaGilouche Icon Theme: Tango Memory status: size: 107462656 vsize: 107462656 resident: 36724736 share: 17768448 rss: 36724736 rss_rlim: 4294967295 CPU usage: start_time: 1176791111 rtime: 232 utime: 206 stime: 26 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/gnome/bin/evolution-2.10' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1234954560 (LWP 668)] [New Thread -1286509680 (LWP 682)] [New Thread -1278092400 (LWP 681)] [New Thread -1268782192 (LWP 679)] [New Thread -1260389488 (LWP 678)] [New Thread -1249928304 (LWP 677)] [New Thread -1241498736 (LWP 674)] (no debugging symbols found) 0xb7fa1410 in __kernel_vsyscall ()
+ Trace 128449
Thread 1 (Thread -1234954560 (LWP 668))
----------- .xsession-errors (214966 sec old) --------------------- empty read empty read empty read empty read empty read empty read empty read empty read empty read empty read empty read empty read empty read empty ...Too much output, ignoring rest... --------------------------------------------------
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. Thanks in advance!
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 373699 ***