gwibber-service crashed with SIGSEGV in __pthread_mutex_lock()

Bug #636241 reported by Antoine Billiau
4
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gwibber

This application crashes, also with version 2.31.92-0ubuntu1 as it did with the previous version.
The crash appears randomly, with ou without using teh application and the crash is not linked with a sequence of programs used (can appear when displaying the Desktop, when working on Openoffice or when browsing).

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.92-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 12 06:41:31 2010
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f4147ede634 <__pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7f4147ede634) ok
 source "0x10(%rdi)" (0x30003cb0) 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 (mutex=0x30003ca0) at pthread_mutex_lock.c:50
 px_proxy_factory_get_proxies () from /usr/lib/libproxy.so.0
 ffi_call_unix64 () from /usr/lib/python2.6/lib-dynload/_ctypes.so
 ffi_call () from /usr/lib/python2.6/lib-dynload/_ctypes.so
 _CallProc () from /usr/lib/python2.6/lib-dynload/_ctypes.so
Title: gwibber-service crashed with SIGSEGV in __pthread_mutex_lock()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Antoine Billiau (antoine-billiau) wrote :
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.