telepathy-logger crashed with SIGSEGV in free()

Bug #731756 reported by Ali Aliev
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-logger (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: telepathy-logger

telepathy-logger crashed with SIGSEGV in free()

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: telepathy-logger 0.2.3-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed Mar 9 06:30:14 2011
ExecutablePath: /usr/lib/telepathy/telepathy-logger
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
ProcCmdline: /usr/lib/telepathy/telepathy-logger
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=ru_RU:en
 LANG=ru_RU.UTF-8
SegvAnalysis:
 Segfault happened at: 0x3a63a9 <free+73>: mov (%eax),%esi
 PC (0x003a63a9) ok
 source "(%eax)" (0x00e00000) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: telepathy-logger
StacktraceTop:
 free () from /lib/libc.so.6
 g_free () from /lib/libglib-2.0.so.0
 ?? () from /usr/lib/libtelepathy-logger.so.2
 _tpl_log_store_add_event () from /usr/lib/libtelepathy-logger.so.2
 _tpl_log_manager_add_event () from /usr/lib/libtelepathy-logger.so.2
Title: telepathy-logger crashed with SIGSEGV in free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #728188, 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.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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