evolution crashed with SIGSEGV in malloc()

[ZaZ213]

Binary package hint: evolution

Crash while switching from mail to contacts. 9.10 release

ProblemType: Crash
Architecture: amd64
Date: Thu Oct 29 20:47:52 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evolution
NonfreeKernelModules: nvidia
Package: evolution 2.28.1-0ubuntu1
ProcCmdline: evolution --component=mail
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7f625bf84ef0: mov 0x8(%r12),%r15
 PC (0x7f625bf84ef0) ok
 source "0x8(%r12)" (0xfec488117b58) not located in a known VMA region (needed readable region)!
 destination "%r15" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 malloc () from /lib/libc.so.6
 ?? () from /usr/lib/libsqlite3.so.0
 ?? () from /usr/lib/libsqlite3.so.0
Title: evolution crashed with SIGSEGV in malloc()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:malloc_consolidate (av=0x7f6244000020) at malloc.c:5089
_int_malloc (av=0x7f6244000020, bytes=129)
*__GI___libc_malloc (bytes=3224) at malloc.c:3638
sqlite3MemMalloc (nByte=3216) at sqlite3.c:12269
mallocWithAlarm (n=3216, pp=0x7f624adf5a28)

[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!.