Ubuntu
gwibber package

gwibber-service crashed with SIGSEGV in free()

Bug #700916 reported by Oweoqi on 2011-01-10

This bug report is a duplicate of: Bug #631147: gwibber-service crashed with SIGSEGV in free(). Edit Remove

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gwibber (Ubuntu)	New	Medium	Unassigned

Bug Description

Binary package hint: gwibber

Occurred while idling

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.32.2-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Jan 10 14:33:04 2011
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate amd64 (20100928)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
LANG=en_AU.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7ffa3cc51c2d <free+29>: mov -0x8(%rdi),%rsi
PC (0x7ffa3cc51c2d) ok
source "-0x8(%rdi)" (0x20002b18) not located in a known VMA region (needed readable region)!
destination "%rsi" ok
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

Tags:

Revision history for this message

Oweoqi (oweoqi) wrote on 2011-01-10:

#1

Dependencies.txt Edit (3.3 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (890 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (67.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (802 bytes, text/plain; charset="utf-8")
Registers.txt Edit (791 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (3.1 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (9.6 KiB, text/plain; charset="utf-8")
gwibber.log.txt Edit (1.2 MiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2011-01-10:

#2

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

Revision history for this message

Apport retracing service (apport) wrote on 2011-01-10: Stacktrace.txt

#3

Stacktrace.txt Edit (12.8 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2011-01-10: ThreadStacktrace.txt

#4

ThreadStacktrace.txt Edit (26.3 KiB, text/plain)

Changed in gwibber (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Victor Vargas (kamus) wrote on 2011-02-21:

#5

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. Please continue to report any other bugs you may find.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #631147 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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