Public bug reported:
Binary package hint: gwibber
it crashed on itself, i didn't use gwibber for a week
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Uname: Linux 2.6.35-6-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Jul 8 13:27:43 2010
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100129)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=it_IT.utf8
SegvAnalysis:
Segfault happened at: 0x7f0f93273644 <pthread_mutex_lock+4>: mov
0x10(%rdi),%esi
PC (0x7f0f93273644) ok
source "0x10(%rdi)" (0x7800dc70) not located in a known VMA region (needed
readable region)!
destination "%esi" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
pthread_mutex_lock () from /lib/libpthread.so.0
px_proxy_factory_get_proxies ()
ffi_call_unix64 ()
ffi_call ()
_CallProc ()
Title: gwibber-service crashed with SIGSEGV in pthread_mutex_lock()
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
vboxusers
** Affects: gwibber (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-crash maverick
--
gwibber-service crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/603117
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
