gwibber-bugs team mailing list archive

[Kamus <kamusin@xxxxxxxxx>]

Shane, please do not submit .crash files into reports. by the way, any
news about this issue?

** Attachment removed: "crash log"
   https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/631147/+attachment/1723169/+files/_usr_bin_gwibber-service.1000.crash

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/631147

Title:
  gwibber-service crashed with SIGSEGV in free()

Status in Gwibber:
  New
Status in “gwibber” package in Ubuntu:
  New

Bug description:
  Binary package hint: gwibber

Gwibber was running in the background and all of a sudden crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.91-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
Architecture: amd64
Date: Sun Sep  5 13:47:45 2010
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x7ffaf8306c2d <free+29>:	mov    -0x8(%rdi),%rsi
 PC (0x7ffaf8306c2d) ok
 source "-0x8(%rdi)" (0xe000afe8) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 free () from /lib/libc.so.6
 ffi_call_unix64 ()
 ffi_call ()
 _CallProc ()
 ?? () from /usr/lib/python2.6/lib-dynload/_ctypes.so
Title: gwibber-service crashed with SIGSEGV in free()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video