telepathy-logger crashed with SIGSEGV in vfprintf()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
telepathy-logger (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
~$ lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
~$ apt-cache policy telepathy-logger
telepathy-logger:
Installiert: 0.4.0-0ubuntu1
Kandidat: 0.4.0-0ubuntu1
Versionstabelle:
*** 0.4.0-0ubuntu1 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-logger 0.4.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-22-generic x86_64
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
Date: Fri Apr 13 20:51:23 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120320)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=de_DE.UTF-8
SegvAnalysis:
Segfault happened at: 0x7fee38f96dba <vfprintf+10042>: repnz scas %es:(%rdi),%al
PC (0x7fee38f96dba) ok
source "%es:(%rdi)" (0x00000048) not located in a known VMA region (needed readable region)!
destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-logger
StacktraceTop:
vfprintf () from /lib/x86_
__vasprintf_chk () from /lib/x86_
g_vasprintf () from /lib/x86_
g_strdup_vprintf () from /lib/x86_
_tpl_debug () from /usr/lib/
Title: telepathy-logger crashed with SIGSEGV in vfprintf()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #973552, 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.