gwibber-service crashed with SIGSEGV in free()

Bug #632672 reported by Dario Castañé
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gwibber

dario@dario-laptop:~$ lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10

gwibber-service:
  Installed: 2.31.91-0ubuntu2
  Candidate: 2.31.91-0ubuntu2
  Version table:
 *** 2.31.91-0ubuntu2 0
        500 http://es.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status

I was configuring my Twitter account. Just after I did it, the error appeared.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.91-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Tue Sep 7 22:22:03 2010
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x7f21a77c2c2d <free+29>: mov -0x8(%rdi),%rsi
 PC (0x7f21a77c2c2d) ok
 source "-0x8(%rdi)" (0x94012c38) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 free () from /lib/libc.so.6
 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 free()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Dario Castañé (i-dario) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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

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.