gwibber-service crashed with SIGSEGV in free()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
Binary package hint: gwibber
Happened after updgrading to Ubunut 10.10 RC
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.32.0-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Fri Oct 1 18:26:13 2010
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.6
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.utf8
SegvAnalysis:
Segfault happened at: 0x7f660ec66c2d <free+29>: mov -0x8(%rdi),%rsi
PC (0x7f660ec66c2d) ok
source "-0x8(%rdi)" (0xf40089a8) 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/
ffi_call () from /usr/lib/
_CallProc () from /usr/lib/
?? () from /usr/lib/
Title: gwibber-service crashed with SIGSEGV in free()
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare vboxusers
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.