Ubuntu
telepathy-logger package

telepathy-logger crashed with SIGSEGV in _tpl_log_manager_add_message()

Bug #700612 reported by Oweoqi on 2011-01-09

This bug report is a duplicate of: Bug #612308: telepathy-logger crashed with SIGSEGV in _tpl_log_manager_add_message(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	telepathy-logger (Ubuntu)	New	Medium	Unassigned

Bug Description

Binary package hint: telepathy-logger

While in chat, messages were being received in triplicate.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: telepathy-logger 0.1.5-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun Jan 9 18:40:11 2011
ExecutablePath: /usr/lib/telepathy/telepathy-logger
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate amd64 (20100928)
ProcCmdline: /usr/lib/telepathy/telepathy-logger
ProcEnviron:
SHELL=/bin/bash
LANG=en_AU.utf8
SegvAnalysis:
Segfault happened at: 0x7fa88ee438f3 <_tpl_log_manager_add_message+371>: mov 0x8(%rax),%r8
PC (0x7fa88ee438f3) ok
source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%r8" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-logger
StacktraceTop:
_tpl_log_manager_add_message () from /usr/lib/libtelepathy-logger.so.1
?? () from /usr/lib/libtelepathy-logger.so.1
?? () from /usr/lib/libtelepathy-logger.so.1
?? () from /usr/lib/libtelepathy-glib.so.0
?? () from /usr/lib/libtelepathy-glib.so.0
Title: telepathy-logger crashed with SIGSEGV in _tpl_log_manager_add_message()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Oweoqi (oweoqi) wrote on 2011-01-09:

Dependencies.txt Edit (787 bytes, text/plain; charset="utf-8")
Disassembly.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (14.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (797 bytes, text/plain; charset="utf-8")
Registers.txt Edit (770 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (2.1 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2011-01-09:

StacktraceTop:
_tpl_log_manager_add_message (
keepon_on_receiving_signal (
on_received_signal_cb (proxy=<value optimized out>,
_tp_cli_channel_type_text_invoke_callback_for_received (tpproxy=0x24f7000, error=<value optimized out>, args=0x24f66c0,
tp_proxy_signal_invocation_run (p=0x24f3500)