ubuntu-bugcontrol team mailing list archive
-
ubuntu-bugcontrol team
-
Mailing list archive
-
Message #02627
[Bug 630890] [NEW] gwibber-service crashed with SIGSEGV in pthread_mutex_lock()
You have been subscribed to a public bug by Apport retracing service (apport):
Binary package hint: gwibber
Crash report on startup.
J
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.91-0ubuntu2
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 5 15:22:09 2010
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
LANG=en_GB.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f6b02b43634 <pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
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.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 lpadmin plugdev sambashare
** Affects: gwibber (Ubuntu)
Importance: Medium
Status: New
** Tags: amd64 apport-crash bugpattern-needed maverick
--
gwibber-service crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.edge.launchpad.net/bugs/630890
You received this bug notification because you are a member of Ubuntu Bug Control, which is a direct subscriber.