evolution-source-registry crashed with SIGSEGV in g_slice_alloc()

Bug #1298526 reported by Anders Pamdal
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution-data-server (Ubuntu)
New
Undecided
Unassigned

Bug Description

...

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: evolution-data-server 3.10.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar 27 15:51:12 2014
ExecutablePath: /usr/lib/evolution/evolution-source-registry
InstallationDate: Installed on 2014-03-04 (22 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: /usr/lib/evolution/evolution-source-registry
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=sv
 PATH=(custom, no user)
 LANG=sv_SE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f84c89af28a <g_slice_alloc+154>: mov 0x8(%rdx),%rbx
 PC (0x7f84c89af28a) ok
 source "0x8(%rdx)" (0x1025c9008) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new_from_bytes () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new_byte () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to trusty on 2014-03-04 (22 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Anders Pamdal (anders-pamdal) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1235177, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.