telepathy-logger crashed with SIGSEGV in tp_asv_get_string()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
telepathy-logger (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Binary package hint: telepathy-logger
loged into my jabber accounts and an error message was shown with "telepathy-logger crashed" or something similar.
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: telepathy-logger 0.1.5-1ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelMo
Architecture: i386
Date: Fri Oct 1 02:04:43 2010
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.utf8
SegvAnalysis:
Segfault happened at: 0x3d8461: test %bh,0x3d845800
PC (0x003d8461) in non-executable VMA region: 0x003d8000-
source "%bh" ok
destination "0x3d845800" (0x3d845800) not located in a known VMA region (needed writable region)!
SegvReason:
executing writable VMA None
writing unknown VMA
Signal: 11
SourcePackage: telepathy-logger
StacktraceTop:
?? () from /lib/libc.so.6
tp_asv_get_string () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: telepathy-logger crashed with SIGSEGV in tp_asv_get_string()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
visibility: | private → public |
StacktraceTop: libtelepathy- logger. so.1 pending_ messages_ cb (proxy=0x8cfa168, dbus_properties _invoke_ callback_ get (
main_arena () from /lib/libc.so.6
?? () from /usr/lib/
tp_asv_get_string (asv=0xc28378, key=0xd858f2 "content")
got_message_
_tp_cli_