GNOME Bugzilla – Bug 360971
crash in Evolution:
Last modified: 2006-10-09 21:13:34 UTC
What were you doing when the application crashed? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 210075648 vsize: 0 resident: 210075648 share: 0 rss: 23830528 rss_rlim: 0 CPU usage: start_time: 1160420444 rtime: 0 utime: 164 stime: 0 cutime:153 cstime: 0 timeout: 11 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1233209680 (LWP 17877)] [New Thread -1318249568 (LWP 17907)] [New Thread -1355838560 (LWP 17903)] [New Thread -1364231264 (LWP 17902)] [New Thread -1389409376 (LWP 17894)] [New Thread -1372623968 (LWP 17891)] [New Thread -1347445856 (LWP 17888)] [New Thread -1339053152 (LWP 17887)] [New Thread -1330660448 (LWP 17886)] [New Thread -1322267744 (LWP 17885)] [New Thread -1286644832 (LWP 17881)] [New Thread -1278252128 (LWP 17880)] [New Thread -1269859424 (LWP 17879)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 75481
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug. Also, 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.
Hi, this is a duplicate of the bug # 360940, I added some traces to that bug, hope it gives you some hints. This bug may be deleted and any debugging proceed with bug no.360940.
Okay, thanks for letting me know, I'll mark as a duplicate. *** This bug has been marked as a duplicate of 360940 ***