GNOME Bugzilla – Bug 615947
Crash immediately after starting when trying to connect to an Exchange server using MAPI
Last modified: 2010-06-14 03:51:44 UTC
Created attachment 158883 [details] Output of running CAMEL_DEBUG=all evolution Using a clean Evolution profile, attempting to connect to an Exchange server using MAPI will crash evolution just after logging in. I am using Evolution 2.30.0 and evolution-mapi 0.30.0, downloaded from projects.gnome.org and compiled from source. I have attached the output of running evolution with the CAMEL_DEBUG=all variable set, and also of running 'gdb evolution'.
Created attachment 158884 [details] Output of running 'gdb evolution'
Pasting traces outside - Program received signal SIGABRT, Aborted. [Switching to Thread 0xb35fbb70 (LWP 21303)] 0x0012d422 in __kernel_vsyscall () (gdb) thread apply all bt
+ Trace 221411
========== 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!
Created attachment 158888 [details] Output of running 'gdb evolution' with debugging symbols enabled I believe this is what you're looking for. This is a full stacktrace obtained after I installed the debugging symbols for evolution-data-server, libgtkhtml, glib, gtk and gnome-vfs.
Thanks. Moving to evolution-mapi.
Joel, traces are missing evolution-mapi related debuginfo. Could you please install debuginfo packages of evolution-mapi and talloc. Next time when you paste gdb traces, please paste the crash point as well. I meant to say these lines above 'thread apply all bt'. Program received signal SIGABRT, Aborted. [Switching to Thread 0xb35fbb70 (LWP 21303)] 0x0012d422 in __kernel_vsyscall () (gdb) thread apply all bt
Created attachment 159320 [details] Output of running 'gdb evolution' (third time lucky) The packages with debugging symbols were not found, so I recompiled talloc and evolution-mapi with the DEB_BUILD_OPTIONS=nostrip,noopt environment variable set. Hopefully this will be enough now to figure out what's happening!
Looks like duplicate of bug 615086 as per https://bugzilla.gnome.org/show_bug.cgi?id=615086#c5
(In reply to comment #7) > Looks like duplicate of bug 615086 Yup, it's the same issue.
*** This bug has been marked as a duplicate of bug 615086 ***