After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 608050 - Segmentation Fault following successful authentication with Exchange 2007 server
Segmentation Fault following successful authentication with Exchange 2007 server
Status: RESOLVED DUPLICATE of bug 578954
Product: evolution-mapi
Classification: Applications
Component: Account Setup Plugin
0.29.x
Other Linux
: High critical
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2010-01-25 17:31 UTC by dwcatcvg
Modified: 2010-01-28 03:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description dwcatcvg 2010-01-25 17:31:38 UTC
Output from evolution (launched from the command line):
Loading profile dcarlso3@NA 
exchange-mapi-connection.c:116: Leaving mapi_profile_load libexchangemapi-Message: exchange-mapi-connection.c:133: exchange_mapi_connection_new: unlock(connect_lock)
libexchangemapi-Message: 
exchange-mapi-connection.c:138: exchange_mapi_connection_new: Connected 

exchange-mapi-connection.c:2660: Entering exchange_mapi_get_folders_list libexchangemapi-Message: exchange-mapi-connection.c:2662: exchange_mapi_get_folders_list: lock(connect_lock)
Segmentation fault

From the System Log Viewer:
Jan 25 12:05:13 ublptp2 kernel: [16649.187953] evolution[5934]: segfault at e1000005 ip 0180f4b4 sp b5010ec0 error 5 in libmapi.so.0.8[17d0000+11a000]

I have no other clues.  I have a profile setup using mapiprofile to test my Exchange server connection, and eveything is OK there -- openchangeclient is able to connect and fetch my messages.
Comment 1 Akhil Laddha 2010-01-27 04:25:34 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 dwcatcvg 2010-01-27 22:14:54 UTC
The closest thing I can give you to a stack trace at the moment (bug-buddy not helping me) is valgrind output:

==15686== Process terminating with default action of signal 11 (SIGSEGV)
==15686==  Access not within mapped region at address 0xE1000005
==15686==    at 0x9D634B4: mapi_object_table_init (in /usr/lib/libmapi.so.0.8)
==15686==    by 0x9D4C3A7: GetHierarchyTable (in /usr/lib/libmapi.so.0.8)
==15686==    by 0x7FD5486: ??? (in /usr/lib/libexchangemapi-1.0.so.0.0.0.pkg)
==15686==    by 0x7FD5F52: exchange_mapi_get_folders_list (in /usr/lib/libexchangemapi-1.0.so.0.0.0.pkg)
==15686==    by 0x7ED2688: ??? (in /usr/lib/evolution-data-server-1.2/camel-providers/libcamelmapi.so)
==15686==    by 0x4288C7B: camel_store_get_folder_info (in /usr/lib/libcamel-provider-1.2.so.14.0.1)
==15686==    by 0x6DA971B: get_folderinfo_exec (mail-ops.c:1073)
==15686==    by 0x6DAD5CF: mail_msg_proxy (mail-mt.c:522)
==15686==    by 0x56059AE: ??? (in /lib/libglib-2.0.so.0.2200.3)
==15686==    by 0x560437E: ??? (in /lib/libglib-2.0.so.0.2200.3)
==15686==    by 0x47D180D: start_thread (pthread_create.c:300)
==15686==    by 0x57248DD: clone (clone.S:130)
==15686==  If you believe this happened as a result of a stack
==15686==  overflow in your program's main thread (unlikely but
==15686==  possible), you can try to increase the size of the
==15686==  main thread stack using the --main-stacksize= flag.
==15686==  The main thread stack size used in this run was 8388608.

Please note I'm trying to build the next version of openchange to get more information about the problem in libmapi.  Having problems with samba4 headers, but will give you more information if I can solve them and get debug info for openchange and evolution-mapi.
Comment 3 dwcatcvg 2010-01-27 22:17:40 UTC
gdb gives exactly the same level of detail as valgrind above.  I have no debug package for openchange or evolution-mapi, so I'm sure there's more information to be had once debug symbols for those packages are visible.
Comment 4 dwcatcvg 2010-01-27 22:52:18 UTC
built libmapi.so.0.9 and got slightly more information about what appears on the surface to be the same problem:

Program received signal SIGSEGV, Segmentation fault.

Thread 3040426864 (LWP 16796)

  • #0 mapi_object_table_init
    at libmapi/mapi_object.c line 319
  • #1 GetHierarchyTable
    at libmapi/IMAPIContainer.c line 276
  • #2 ??
    from /usr/lib/libexchangemapi-1.0.so.0
  • #3 exchange_mapi_get_folders_list
    from /usr/lib/libexchangemapi-1.0.so.0
  • #4 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelmapi.so
  • #5 camel_store_get_folder_info
    from /usr/lib/libcamel-provider-1.2.so.14
  • #6 get_folderinfo_exec
    at mail-ops.c line 1073
  • #7 mail_msg_proxy
    at mail-mt.c line 522
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 ??
    from /lib/libglib-2.0.so.0
  • #10 start_thread
    at pthread_create.c line 300
  • #11 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130

Comment 5 Akhil Laddha 2010-01-28 03:47:36 UTC
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 bug 578954 ***