[Lucid] evolution crashed with SIGSEGV in memcpy()

[Matej Kenda]

Binary package hint: evolution

The crash was reported when Evolution was starting up. I use Exchange server mailbox. Exchange integration crashed at the same time as well.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: evolution 2.28.3-0ubuntu8
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
Architecture: amd64
Date: Wed Apr 7 10:02:36 2010
ExecutablePath: /usr/bin/evolution
ProcCmdline: evolution
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f4d9234dcd3 <memcpy+163>: mov %al,(%rdi)
 PC (0x7f4d9234dcd3) ok
 source "%al" ok
 destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 memcpy () at ../sysdeps/x86_64/memcpy.S:162
 ?? ()
 ?? ()
 camel_stub_marshal_decode_string ()
 ?? ()
Title: evolution crashed with SIGSEGV in memcpy()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
XsessionErrors: (polkit-gnome-authentication-agent-1:2026): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Apport retracing service (apport)]

StacktraceTop:
 memcpy () at ../sysdeps/x86_64/memcpy.S:162
 marshal_read (marshal=0x7f4d80035f10, buf=0x0,
 decode_string (marshal=0x7f4d80035f10,
 camel_stub_marshal_decode_string (marshal=0x0,
 stub_send_internal (stub=0x1ecd1e0,

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.