gwibber-service crashed with SIGSEGV in pthread_mutex_lock()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
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
ProcVersionSign
Uname: Linux 2.6.35-6-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Thu Jul 8 13:27:43 2010
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100129)
InterpreterPath: /usr/bin/python2.6
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=it_IT.utf8
SegvAnalysis:
Segfault happened at: 0x7f0f93273644 <pthread_
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
px_proxy_
ffi_call_unix64 ()
ffi_call ()
_CallProc ()
Title: gwibber-service crashed with SIGSEGV in pthread_
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare vboxusers
I get this crash every time I try to add my facebook account