gwibber-service crashed with SIGSEGV in __libc_free()

Bug #640884 reported by Tim Penhey
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gwibber

I'm pretty sure this occurred during an attempt to suspend.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.94-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-21.31-generic 2.6.35.4
Uname: Linux 2.6.35-21-generic x86_64
Architecture: amd64
Date: Fri Sep 17 08:48:08 2010
ExecutablePath: /usr/bin/gwibber-service
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_NZ.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f3302e3ec2d <__libc_free+29>: mov -0x8(%rdi),%rsi
 PC (0x7f3302e3ec2d) ok
 source "-0x8(%rdi)" (0xec002ee8) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 __libc_free (mem=0xec002ef0) at malloc.c:3709
 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
 ?? () from /usr/lib/python2.6/lib-dynload/_ctypes.so
Title: gwibber-service crashed with SIGSEGV in __libc_free()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Tim Penhey (thumper) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 *__GI___libc_free (mem=0xec002ef0) at malloc.c:3709
 ffi_call_unix64 ()
 ffi_call ()
 _CallProc (pProc=<value optimized out>,
 CFuncPtr_call (self=0x2f26940, inargs=0x3043490,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gwibber (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Victor Vargas (kamus) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 631147, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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.