telepathy-logger crashed with SIGSEGV in vfprintf()

Bug #1078375 reported by Muelli
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-logger (Ubuntu)
New
Undecided
Unassigned

Bug Description

I just used the debug window

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-logger 0.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
Uname: Linux 3.2.0-32-generic x86_64
ApportVersion: 2.0.1-0ubuntu15
Architecture: amd64
CrashCounter: 1
Date: Tue Nov 13 17:28:07 2012
ExecutablePath: /usr/lib/telepathy/telepathy-logger
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110201.2)
MarkForUpload: True
ProcCmdline: /usr/lib/telepathy/telepathy-logger
SegvAnalysis:
 Segfault happened at: 0x7fa6abfc33b1 <vfprintf+10737>: repnz scas %es:(%rdi),%al
 PC (0x7fa6abfc33b1) 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_64-linux-gnu/libc.so.6
 __vasprintf_chk () from /lib/x86_64-linux-gnu/libc.so.6
 g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 _tpl_debug () from /usr/lib/x86_64-linux-gnu/libtelepathy-logger.so.2
Title: telepathy-logger crashed with SIGSEGV in vfprintf()
UpgradeStatus: Upgraded to precise on 2012-09-06 (68 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Muelli (ubuntu-bugs-auftrags-killer) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.