*** This bug is a duplicate of bug 973552 ***
    https://bugs.launchpad.net/bugs/973552

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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1051681/+attachment/3319106/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1051681/+attachment/3319108/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1051681/+attachment/3319110/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1051681/+attachment/3319111/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1051681/+attachment/3319112/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1051681/+attachment/3319113/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1051681/+attachment/3319114/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 973552
   telepathy-logger crashed with SIGSEGV in _IO_vfprintf_internal()

** Visibility changed to: Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-logger in Ubuntu.
https://bugs.launchpad.net/bugs/1051681

Title:
  telepathy-logger crashed with SIGSEGV in vfprintf()

Status in “telepathy-logger” package in Ubuntu:
  New

Bug description:
  Had a gtalk audio conversation it disconnected and crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: telepathy-logger 0.4.0-1
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  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/telepathy/telepathy-logger
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcCmdline: /usr/lib/telepathy/telepathy-logger
  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_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 quantal on 2012-09-08 (8 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-logger/+bug/1051681/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to