evolution crashed with SIGSEGV in e_error_newv()

[lelamal]

Binary package hint: evolution

I was changing folders when Evolution froze for a dozen seconds before crashing.

ProblemType: Crash
Architecture: i386
Date: Wed Feb 3 01:34:06 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: evolution 2.28.1-0ubuntu2
ProcCmdline: evolution --component=mail
ProcCwd: /home/lelamal
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SegvAnalysis:
 Segfault happened at: 0x1cb768: movzbl (%edi),%eax
 PC (0x001cb768) ok
 source "(%edi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /usr/lib/evolution/2.28/libeutil.so.0
 e_error_newv () from /usr/lib/evolution/2.28/libeutil.so.0
 e_error_new () from /usr/lib/evolution/2.28/libeutil.so.0
 mail_msg_check_error ()
 ?? ()
Title: evolution crashed with SIGSEGV in e_error_newv()
Uname: Linux 2.6.31-17-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Pedro Villavicencio (pedro)]

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[lelamal (lelamal-deactivatedaccount)]

Thank you for your reply. I would be very happy to help. However, I have read the page you link several times already, even in the past, and always failed to understand what am I supposed to do. I find the explanation convoluted and unclear. Where it reads: "First, check if there is a package with a -dbg suffix in the main Ubuntu repositories (TODO: Please edit this wiki here to describe how to do this). These are the debug symbol packages, and are equivalent to '-dbgsym' described below. You can safely use either one, but not both at once", I don't know how to proceed. If you can guide me through this whole process, I would be very happy to help. Otherwise, I will try to click on the crash file in var>crash. The reason why I uploaded a short report is that the full report, over 250 MB, always fails in the end alleging some connection problem. If this also fails, you can safely close this bug, for I will not attempt what I did not understand. Thank you.

[Pedro Villavicencio (pedro)]

no worries, let's close this bug for now, please test with lucid to see if you're able to reproduce it and comment back later, thanks.