GNOME Bugzilla – Bug 355966
crash in Evolution: <Ctl><a> and <ctl><d> in...
Last modified: 2006-09-17 14:02:13 UTC
What were you doing when the application crashed? <Ctl><a> and <ctl><d> in a folder Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 35495936 vsize: 0 resident: 179056640 share: 0 rss: 179056640 rss_rlim: 0 CPU usage: start_time: 427 rtime: 0 utime: 1158244002 stime: 0 cutime:3216 cstime: 0 timeout: 3010 it_real_value: 0 frequency: 206 Backtrace was generated from '/usr/bin/evolution-2.8' (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 805589216 (LWP 6504)] [New Thread 888911088 (LWP 6745)] [New Thread 880112880 (LWP 6597)] [New Thread 871724272 (LWP 6592)] [New Thread 851678448 (LWP 6524)] [New Thread 843289840 (LWP 6521)] [New Thread 834901232 (LWP 6513)] [New Thread 825849072 (LWP 6511)] 0x0ea10220 in __waitpid_nocancel () from /lib/libc.so.6
+ Trace 72341
Thread 8 (Thread 825849072 (LWP 6511))
Thread 6 (Thread 843289840 (LWP 6521))
Thread 5 (Thread 851678448 (LWP 6524))
Thread 4 (Thread 871724272 (LWP 6592))
Thread 3 (Thread 880112880 (LWP 6597))
Thread 2 (Thread 888911088 (LWP 6745))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Okay, here's a copy/paste from BugBuddy. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 32890880 vsize: 0 resident: 131534848 share: 0 rss: 131534848 rss_rlim: 0 CPU usage: start_time: 7439 rtime: 0 utime: 1158428666 stime: 0 cutime:1679 cstime: 0 timeout: 1606 it_real_value: 0 frequency: 73 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 805593312 (LWP 10504)] [New Thread 871519472 (LWP 10526)] [New Thread 863130864 (LWP 10521)] [New Thread 843023600 (LWP 10516)] [New Thread 834241776 (LWP 10514)] [New Thread 825849072 (LWP 10512)] 0x0ea1f220 in __waitpid_nocancel () from /lib/libc.so.6
+ Trace 72510
Thread 1 (Thread 805593312 (LWP 10504))
Thanks for the good stacktrace, digger. :) 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 330728 ***