gwibber-service crashed with SIGSEGV in free()

Bug #694205 reported by eduardo30
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gwibber

I was adding my Facebook account under a live session when it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.32.0.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Fri Dec 24 14:15:52 2010
ExecutablePath: /usr/bin/gwibber-service
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fb6655d4c2d <free+29>: mov -0x8(%rdi),%rsi
 PC (0x7fb6655d4c2d) ok
 source "-0x8(%rdi)" (0x500088b8) 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

Revision history for this message
eduardo30 (eduardocarrillo30) wrote :
Revision history for this message
Victor Vargas (kamus) wrote :

Do you have persistence in this live session (usb drive) or just occurr while you are using a CD?

Changed in gwibber (Ubuntu):
importance: Undecided → Medium
Robert Sajdok (ris)
Changed in gwibber (Ubuntu):
status: New → Incomplete
Revision history for this message
Victor Vargas (kamus) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in gwibber (Ubuntu):
status: Incomplete → Invalid
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.