evolution crashed with SIGSEGV in __find_specmb()

Bug #799414 reported by Paul Ortyl
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: evolution

while browsing mail...

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: evolution 2.32.2-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Sun Jun 19 15:58:28 2011
ExecutablePath: /usr/bin/evolution
ProcCmdline: evolution
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LC_MESSAGES=en_US.UTF-8
 LANG=en_GB.utf8
 LANGUAGE=en_US:en
SegvAnalysis:
 Segfault happened at: 0x7f88ab0bf8fa <_IO_vfprintf_internal+154>: callq 0x7f88ab105dc0 <strchrnul>
 PC (0x7f88ab0bf8fa) ok
 source "0x7f88ab105dc0" (0x7f88ab105dc0) ok
 destination "(%rsp)" (0x7f8879841ff0) in non-writable VMA region: 0x7f8879841000-0x7f8879842000 ---p None
 Stack memory exhausted (SP below stack segment)
SegvReason: writing VMA None
Signal: 11
SourcePackage: evolution
StacktraceTop:
 __find_specmb (s=0x7f8879842680, format=0x7f88b0bcfc95 "%s/%s", ap=0x7f88798427f0) at printf-parse.h:99
 _IO_vfprintf_internal (s=0x7f8879842680, format=0x7f88b0bcfc95 "%s/%s", ap=0x7f88798427f0) at vfprintf.c:1325
 __vasprintf_chk (result_ptr=0x7f88798427d8, flags=1, format=0x7f88b0bcfc95 "%s/%s", args=0x7f88798427f0) at vasprintf_chk.c:68
 g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: evolution crashed with SIGSEGV in __find_specmb()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Paul Ortyl (ortylp) wrote :
Revision history for this message
Paul Ortyl (ortylp) wrote :

crashed repeatedly until I cleared the "spam" inbox using different email client
=> security relevant?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

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.

Changed in evolution (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Paul Ortyl (ortylp) wrote :

Stack trace suggests infinite recursion...

If you tell me frame number and variable name, then maybe I'll be able recover the text of the offending spam email.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for evolution (Ubuntu) because there has been no activity for 60 days.]

Changed in evolution (Ubuntu):
status: Incomplete → Expired
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.