GNOME Bugzilla – Bug 429984
crash in Evolution: I've just started Evolut...
Last modified: 2007-04-26 11:15:17 UTC
What were you doing when the application crashed? I've just started Evolution first time after the installation and it crashed immediately Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 255152128 vsize: 255152128 resident: 28540928 share: 16482304 rss: 28540928 rss_rlim: -1 CPU usage: start_time: 1176645774 rtime: 93 utime: 87 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 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 47924037217648 (LWP 8012)] (no debugging symbols found) 0x00002b962aeb05cf in waitpid () from /lib/libc.so.6
+ Trace 127967
Thread 1 (Thread 47924037217648 (LWP 8012))
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!
(In reply to comment #1) > 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 your attention. Unfortunately, there is no evolution-dbgsym package for evolution-2.8.1-0ubuntu4.1, but only for evolution-2.8.1-0ubuntu4. So I can not provide detailed stack trace. Please advise me if I've done something wrong. Thanks.
Here is a stack trace from GDB
+ Trace 130682
Thread 1 (Thread 47651048025456 (LWP 15835))
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 425129 ***