gwibber-service crashed with SIGSEGV in pthread_mutex_lock()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gwibber |
Fix Released
|
High
|
Ken VanDine | ||
gwibber (Ubuntu) |
Fix Released
|
High
|
Ken VanDine |
Bug Description
Binary package hint: gwibber
i had recently had a desktop-couch crash, so may be related to that
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.1-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-6-generic x86_64
Architecture: amd64
Date: Tue Jun 29 23:14:21 2010
ExecutablePath: /usr/bin/
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100629)
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7fd3d9aaf644 <pthread_
PC (0x7fd3d9aaf644) ok
source "0x10(%rdi)" (0xc41ae800) 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
visibility: | private → public |
Changed in gwibber (Ubuntu): | |
status: | Incomplete → New |
Changed in gwibber (Ubuntu): | |
status: | New → Confirmed |
Changed in gwibber: | |
assignee: | nobody → Ken VanDine (ken-vandine) |
importance: | Undecided → High |
milestone: | none → 2.32.0 |
status: | New → Fix Committed |
Changed in gwibber (Ubuntu): | |
importance: | Medium → High |
Changed in gwibber: | |
status: | Fix Committed → Fix Released |
StacktraceTop: .so.0 factory_ get_proxies (self=0xc41ae7f0, ba20,
pthread_mutex_lock () from /lib/libpthread
px_proxy_
ffi_call_unix64 ()
ffi_call (cif=0x7fd3c3ff
_CallProc (pProc=<value optimized out>,