gwibber-service crashed with SIGSEGV in ffi_call_unix64()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crash from Ubuntu 13.04
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gwibber-service 3.6.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.8.0-7-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Sun Feb 24 22:35:43 2013
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2013-02-15 (9 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f959e2f9cc6: cmp %rbp,(%rax)
PC (0x7f959e2f9cc6) ok
source "%rbp" ok
destination "(%rax)" (0x700000008) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
?? () from /usr/lib/
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
g_cclosure_
g_closure_invoke () from /usr/lib/
Title: gwibber-service crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: Upgraded to raring on 2013-02-20 (4 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1123780, so 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.