telepathy-logger crashed with SIGSEGV in vfprintf()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
telepathy-logger (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Had a gtalk audio conversation it disconnected and crash.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: telepathy-logger 0.4.0-1
ProcVersionSign
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Sun Sep 16 20:44:23 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7fc53149bd7a <vfprintf+10042>: repnz scas %es:(%rdi),%al
PC (0x7fc53149bd7a) ok
source "%es:(%rdi)" (0x00000010) 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: Upgraded to quantal on 2012-09-08 (8 days ago)
UserGroups: adm cdrom dip libvirtd 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.