qutimdevelop team mailing list archive

[Tretyakov R <roman@xxxxxxxx>]

** Changed in: qutim
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of QutIM
Developers, which is subscribed to qutim.
https://bugs.launchpad.net/bugs/1026194

Title:
  qutim crashed with SIGSEGV in QIODevice::read()

Status in Multiplatform instant messenger:
  Fix Released

Bug description:
  Just crashed when it was in foreground with one active chat

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: qutim 0.3.0+201204270619-33~oneiric1
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: amd64
  CrashCounter: 1
  CrashDB: qutim
  Date: Wed Jul 18 19:29:25 2012
  ExecutablePath: /usr/bin/qutim
  LocalModules:
   
  ProcCmdline: qutim --single-instance
  SegvAnalysis:
   Segfault happened at: 0x7f87fca90990 <_ZN9QIODevice4readEPcx+48>:	mov    0x98(%rbx),%r14d
   PC (0x7f87fca90990) ok
   source "0x98(%rbx)" (0x00000098) not located in a known VMA region (needed readable region)!
   destination "%r14d" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: qutim
  StacktraceTop:
   QIODevice::read(char*, long long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
   QIODevice::read(long long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
   ?? () from /usr/lib/qutim/plugins/liboscar.so
   ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
   start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
  ThirdParty: True
  Title: qutim crashed with SIGSEGV in QIODevice::read()
  UpgradeStatus: Upgraded to precise on 2012-07-14 (3 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/qutim/+bug/1026194/+subscriptions