evolution crashed with SIGSEGV in g_hash_table_foreach()

Bug #417817 reported by Thomas Bechtold
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: evolution

i selected about 20 messages and marked the 20 messages as Spam. Then evolution crashed.

ProblemType: Crash
Architecture: i386
Date: Sun Aug 23 21:00:59 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evolution
NonfreeKernelModules: wl nvidia
Package: evolution 2.27.90-0ubuntu2
ProcCmdline: evolution --component=mail
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-6.26-generic
SegvAnalysis:
 Segfault happened at: 0x3908e7: mov (%eax),%eax
 PC (0x003908e7) ok
 source "(%eax)" (0x00000001) 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/libcamel-provider-1.2.so.14
 ?? () from /usr/lib/libcamel-provider-1.2.so.14
 g_hash_table_foreach () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libcamel-provider-1.2.so.14
 camel_folder_summary_save_to_db ()
Title: evolution crashed with SIGSEGV in g_hash_table_foreach()
Uname: Linux 2.6.31-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Thomas Bechtold (toabctl) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:message_info_to_db (s=0xabd49948, info=0x8d02c48)
save_to_db_cb (key=0xa5f73df0, value=0x8d02c48,
IA__g_hash_table_foreach (hash_table=0xb3a64180,
save_message_infos_to_db (s=0xabd49948,
camel_folder_summary_save_to_db (s=0xabd49948,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in evolution (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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.

Changed in evolution (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.