GNOME Bugzilla – Bug 442154
crash in Evolution Mail: Filtrando mensajes con s...
Last modified: 2007-06-11 11:53:02 UTC
What were you doing when the application crashed? Filtrando mensajes con spamassassin. Distribution: Debian lenny/sid Gnome Release: 2.18.2 2007-05-28 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.18-4-amd64 #1 SMP Mon Mar 26 11:36:53 CEST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks-LemonGraphite Icon Theme: KearonesComiconsLight Memory status: size: 385863680 vsize: 385863680 resident: 32653312 share: 19492864 rss: 32653312 rss_rlim: 18446744073709551615 CPU usage: start_time: 1180470000 rtime: 111 utime: 94 stime: 17 cutime:0 cstime: 0 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47705278158256 (LWP 5253)] [New Thread 1132489024 (LWP 5285)] [New Thread 1124096320 (LWP 5284)] [New Thread 1115703616 (LWP 5267)] [New Thread 1107310912 (LWP 5265)] [New Thread 1098918208 (LWP 5263)] [New Thread 1090525504 (LWP 5262)] [New Thread 1082132800 (LWP 5260)] (no debugging symbols found) 0x00002b633957ac9f in waitpid () from /lib/libpthread.so.0
+ Trace 136696
Thread 1 (Thread 47705278158256 (LWP 5253))
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 ***