evolution crashed with SIGSEGV in mail_msg_unref()

Bug #602928 reported by Petko Kolenichev
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Evolution
Expired
Critical
evolution (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: evolution

Hi my development branch of ubuntu is just updated with latest package. Evolution with MAPI plugin still crashes on start, when it process deleted message.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: evolution 2.30.2-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Uname: Linux 2.6.35-6-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Jul 8 01:19:15 2010
ExecutablePath: /usr/bin/evolution
ProcCmdline: evolution
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=bg_BG:bg:en_GB:en
 LANG=bg_BG.utf8
SegvAnalysis:
 Segfault happened at: 0x7fd1ff2c5764 <mail_msg_unref+36>: mov 0x8(%rdi),%eax
 PC (0x7fd1ff2c5764) ok
 source "0x8(%rdi)" (0x4a1b1c000000002b) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 mail_msg_unref (msg=0x4a1b1c0000000023) at mail-mt.c:177
 ms_thread_msg_free (session=0x281f170, m=
 g_thread_pool_thread_proxy (
 g_thread_create_proxy (data=0x7fd1e40c1fb0)
 start_thread () from /lib/libpthread.so.0
Title: evolution crashed with SIGSEGV in mail_msg_unref()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse kqemu kvm libvirtd lpadmin netdev plugdev sambashare vboxusers video

Revision history for this message
Petko Kolenichev (pkolenichev) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 mail_msg_unref ()
 ?? ()
 g_thread_pool_thread_proxy (
 g_thread_create_proxy (data=0x7fd1e40c1fb0)
 start_thread () from /lib/libpthread.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in evolution (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
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):
status: New → Incomplete
Revision history for this message
Petko Kolenichev (pkolenichev) wrote :

gdb-evolution.txt

Revision history for this message
Petko Kolenichev (pkolenichev) wrote :

Hi I was using https://wiki.ubuntu.com/X/Backtracing --> section Backtrace with gdb to generate gdb-evolution.txt file. Please let me know if it is what you need.

Thank you!
Petko

Randy Barlow (rbarlow)
Changed in evolution (Ubuntu):
status: Incomplete → New
Revision history for this message
Randy Barlow (rbarlow) wrote :

I just updated to evolution 2.30.2-1ubuntu2 with evolution-mapi 0.28.3-0ubuntu1 and the problem still exists.

Revision history for this message
Randy Barlow (rbarlow) wrote :

Problem still happens with evolution 2.30.3-1ubuntu1 and evolution-mapi 0.28.3-0ubuntu1.

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

Could you execute 'backtrace' in gdb and also 'thread apply all bt full' after getting the crash and attach the resulting output to the report? you were doing the right thing to get the backtrace but looks like you didn't executed the command which shows the backtrace. Thanks again.

Revision history for this message
Randy Barlow (rbarlow) wrote :

This is the requested backtrace info, thanks!

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

Hello Randy, I've checked the upstream bts and talked with some bugsquad members and the crash seems unique, but we'd like to get some full debugging on it, could you install the libglib2, libgtk2 and just in case evolution-data-server and evolution dbgsym packages and get a new one performing the exact same steps you did before? that'd help us a lot , thanks again!.

Revision history for this message
Randy Barlow (rbarlow) wrote :

Here is the gdb session with all the requested debugging symbols installed.

Revision history for this message
Randy Barlow (rbarlow) wrote :

I went ahead an ran valgrind on evolution as well since it is a segmentation fault.

Revision history for this message
Petko Kolenichev (pkolenichev) wrote : Re: [Bug 602928] Re: evolution crashed with SIGSEGV in mail_msg_unref()

Hi Pedro,

 I sill experience the same problem. Please find attached requested gdb

Petko Kolenichev

mobile BG: +359 88 683 6061

On Thu, Sep 9, 2010 at 7:04 PM, Randy Barlow <email address hidden>wrote:

> I went ahead an ran valgrind on evolution as well since it is a
> segmentation fault.
>
> ** Attachment added: "valgrind output"
>
> https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/602928/+attachment/1561260/+files/valgrind-logs-evolution.tar.bz2
>
> --
> evolution crashed with SIGSEGV in mail_msg_unref()
> https://bugs.launchpad.net/bugs/602928
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “evolution” package in Ubuntu: New
>
> Bug description:
> Binary package hint: evolution
>
> Hi my development branch of ubuntu is just updated with latest package.
> Evolution with MAPI plugin still crashes on start, when it process deleted
> message.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 10.10
> Package: evolution 2.30.2-0ubuntu4
> ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
> Uname: Linux 2.6.35-6-generic x86_64
> Architecture: amd64
> CrashCounter: 1
> Date: Thu Jul 8 01:19:15 2010
> ExecutablePath: /usr/bin/evolution
> ProcCmdline: evolution
> ProcEnviron:
> SHELL=/bin/bash
> LANGUAGE=bg_BG:bg:en_GB:en
> LANG=bg_BG.utf8
> SegvAnalysis:
> Segfault happened at: 0x7fd1ff2c5764 <mail_msg_unref+36>: mov
> 0x8(%rdi),%eax
> PC (0x7fd1ff2c5764) ok
> source "0x8(%rdi)" (0x4a1b1c000000002b) not located in a known VMA region
> (needed readable region)!
> destination "%eax" ok
> Stack memory exhausted (SP below stack segment)
> SegvReason: reading unknown VMA
> Signal: 11
> SourcePackage: evolution
> StacktraceTop:
> mail_msg_unref (msg=0x4a1b1c0000000023) at mail-mt.c:177
> ms_thread_msg_free (session=0x281f170, m=
> g_thread_pool_thread_proxy (
> g_thread_create_proxy (data=0x7fd1e40c1fb0)
> start_thread () from /lib/libpthread.so.0
> Title: evolution crashed with SIGSEGV in mail_msg_unref()
> UserGroups: adm admin audio cdrom dialout dip fax floppy fuse kqemu kvm
> libvirtd lpadmin netdev plugdev sambashare vboxusers video
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/602928/+subscribe
>

Revision history for this message
Petko Kolenichev (pkolenichev) wrote :

Hi Pedro,

I still experience the same problem. Please find attached requested gdb after installing the requested packages.

thank you,
Petko

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

that was fast!, thank you folks, i'll send this upstream.

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

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=629193

Changed in evolution (Ubuntu):
status: New → Triaged
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Hello folks, the upstream developers are asking for another trace with pango debug symbols, could you install libpango1.0-0-dbgsym and get a new backtrace? thanks a lot.

Revision history for this message
Randy Barlow (rbarlow) wrote :

I've installed the debug symbols for Pango, and here is the backtrace.

Revision history for this message
Randy Barlow (rbarlow) wrote :

BTW, I did already put this on the upstream bug report for you. I thought the traceback was strange though, as it did not contain the string "pango" anymore, so it may not be that useful.

Revision history for this message
Petko Kolenichev (pkolenichev) wrote :

Hi Pedro,
please find attached backtrace after installing libpango1.0-0-dbgsym.
Best Regards!

Changed in evolution:
importance: Unknown → Critical
status: Unknown → Incomplete
Revision history for this message
Randy Barlow (rbarlow) wrote :

The latest versions of evolution (2.30.3-1ubuntu6) and evolution-mapi
(0.30.3-1ubuntu1) in Ubuntu Maverick allow me to read my mail without this
crash.

Changed in evolution:
status: Incomplete → New
Changed in evolution:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

still an issue on 2.32 ?

Changed in evolution (Ubuntu):
status: Triaged → Incomplete
Changed in evolution:
status: Incomplete → Expired
Revision history for this message
Pedro Villavicencio (pedro) wrote :

closing the bug then, thanks much.

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