GNOME Bugzilla – Bug 360001
crash in Evolution: Switched to looking at t...
Last modified: 2006-10-06 02:41:17 UTC
What were you doing when the application crashed? Switched to looking at the 'junk' folder. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 192319488 vsize: 0 resident: 192319488 share: 0 rss: 39305216 rss_rlim: 0 CPU usage: start_time: 1160078442 rtime: 0 utime: 967 stime: 0 cutime:872 cstime: 0 timeout: 95 it_real_value: 0 frequency: 30 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 -1233238352 (LWP 9385)] [New Thread -1373021280 (LWP 9446)] [New Thread -1355277408 (LWP 9432)] [New Thread -1301075040 (LWP 9431)] [New Thread -1275491424 (LWP 9410)] [New Thread -1318253664 (LWP 9409)] [New Thread -1335039072 (LWP 9408)] [New Thread -1326646368 (LWP 9407)] [New Thread -1309860960 (LWP 9405)] [New Thread -1292682336 (LWP 9403)] [New Thread -1283884128 (LWP 9402)] [New Thread -1267098720 (LWP 9400)] [New Thread -1258706016 (LWP 9399)] [New Thread -1249535072 (LWP 9398)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 74775
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.
After installing the Ubuntu gnome debugging libraries, I think I managed to reproduce the problem. I let bugbuddy collect the trace, and so it opened case 360017 to track it. Hope the new trace helps... Cheers, Trond
Thanks for your efforts and fast response. :) Marking this one as a duplicate of the later filed bug 360017, which got a stacktrace with debugging symbols. *** This bug has been marked as a duplicate of 360017 ***