telepathy-logger crashed with SIGSEGV in __libc_free()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
telepathy-logger (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: telepathy-logger
Telepathy logger crashed on a huge amount of tweets received via jabber in empathy.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: telepathy-logger 0.2.1-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-
Architecture: i386
CheckboxSubmission: c4273c0f4f2b8d2
CheckboxSystem: a871981cb5bdf4d
Date: Sat Feb 26 23:18:37 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANGUAGE=
LANG=fr_FR.UTF-8
SegvAnalysis:
Segfault happened at: 0xb740a43c <__libc_free+92>: lock cmpxchg %ecx,(%esi)
PC (0xb740a43c) ok
source "%ecx" ok
destination "(%esi)" (0x746e656d) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: telepathy-logger
StacktraceTop:
__libc_free (mem=0xb77b4b40) at malloc.c:3736
g_free (mem=0xb77b4b40) at /build/
?? () from /usr/lib/
_tpl_log_
_tpl_log_
Title: telepathy-logger crashed with SIGSEGV in __libc_free()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev pulse pulse-access scanner tape users video
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 #725512, 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.