GNOME Bugzilla – Bug 357608
Crash in g_str_hash, e_cal_backend_exchange_add_object
Last modified: 2010-05-10 04:24:04 UTC
What were you doing when the application crashed? I opened up my Exchange calendar Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 201355264 vsize: 0 resident: 201355264 share: 0 rss: 32575488 rss_rlim: 0 CPU usage: start_time: 1159190535 rtime: 0 utime: 532 stime: 0 cutime:484 cstime: 0 timeout: 48 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 -1233340752 (LWP 11650)] [New Thread -1399448672 (LWP 11898)] [New Thread -1357218912 (LWP 11720)] [New Thread -1348826208 (LWP 11719)] [New Thread -1337660512 (LWP 11670)] [New Thread -1329267808 (LWP 11669)] [New Thread -1280193632 (LWP 11658)] [New Thread -1270047840 (LWP 11656)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 73198
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. Can you reproduce the crash, Toni?
Here's a new bug report with debugging symbols (at least I think this is the same bug). I'm running Ubuntu Edgy. Any other debuging symbol packages I should install? Memory status: size: 76890112 vsize: 0 resident: 76890112 share: 0 rss: 23134208 rss_rlim: 0 CPU usage: start_time: 1159206541 rtime: 0 utime: 582 stime: 0 cutime:510 cstime: 0 timeout: 72 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/evolution-exchange' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1234250064 (LWP 4646)] [New Thread -1266877536 (LWP 5128)] [New Thread -1234429024 (LWP 4651)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 73225
Thread 2 (Thread -1266877536 (LWP 5128))
According to bug 357652 comment 0 (same reporter), this *may* be the same issue. However, the stacktraces do look totally different... Reopening, cause the info asked for has been provided. Thanks Toni.
New backtrace at: https://launchpad.net/distros/ubuntu/+source/evolution-exchange/+bug/62297/comments/7
Backtrace from the Ubuntu bug: 0xffffe410 in __kernel_vsyscall ()
+ Trace 90789
Still a problem on evo 2.24.0. I think enough information is included here for work to be done on it.
(In reply to comment #5) > Backtrace from the Ubuntu bug: > > [...] Info posted at ubuntu bug actually is: Here's another one. Though I guesss libc6-dbg doesn't really work because it's using libc6-i686, right? Should I find a libc6-i686-dbg somewhere? Memory status: size: 81141760 vsize: 0 resident: 81141760 share: 0 rss: 14254080 rss_rlim: 0 CPU usage: start_time: 1160385318 rtime: 0 utime: 1270 stime: 0 cutime:1159 cstime: 0 timeout: 111 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/evolution-exchange' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1233926480 (LWP 30869)] [New Thread -1277170784 (LWP 15550)] [New Thread -1268778080 (LWP 15548)] [New Thread -1258292320 (LWP 15515)] [New Thread -1235653728 (LWP 30871)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 210902
Thread 4 (Thread -1258292320 (LWP 15515))
*** Bug 571493 has been marked as a duplicate of this bug. ***
exchange-storage process is not a separate process any more in upcoming 2.30.0. This version is no longer maintained, which means that it will not receive any further security or bug fix updates. The current stable GNOME and Evolution version is 2.30. Can you please check again whether this issue still happens in Evolution 2.28 or 2.30 and update this report by adding a comment and changing the "Version" field? Thanks a lot. Again thank you for reporting this bug and we are sorry it could not be fixed for the version you originally used here. Without feedback this report will be closed as INCOMPLETE in 6 weeks.
Closing this bug report as no further information has been provided. Please feel free to reopen the bug if the problem still occurs with a newer version of GNOME 2.30.0 or later, thanks.