gwibber-service crashed with SIGSEGV in pthread_mutex_lock()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: gwibber
Crash report on startup.
J
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.91-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.35-19-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 5 15:22:09 2010
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
LANG=en_GB.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f6b02b43634 <pthread_
PC (0x7f6b02b43634) ok
source "0x10(%rdi)" (0xec02f2a0) 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 lpadmin plugdev sambashare
tags: | added: bugpattern-needed |
StacktraceTop: .so.0 factory_ get_proxies (self=0xec02f290,
pthread_mutex_lock () from /lib/libpthread
px_proxy_
ffi_call_unix64 ()
ffi_call ()
_CallProc (pProc=<value optimized out>,