scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libunity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
no idea what triggered this
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-scopes-runner 7.0.12+
ProcVersionSign
Uname: Linux 3.11.0-3-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Tue Aug 20 17:01:17 2013
Dependencies:
EcryptfsInUse: Yes
ExecutablePath: /usr/share/
InstallationDate: Installed on 2012-01-04 (594 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120104)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/share/
SegvAnalysis:
Segfault happened at: 0x7ffbc75558be: cmp %rbp,(%rax)
PC (0x7ffbc75558be) ok
source "%rbp" ok
destination "(%rax)" (0x700000001) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: libunity
StacktraceTop:
?? () from /usr/lib/
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
g_cclosure_
g_closure_invoke () from /usr/lib/
Title: scope-runner-
UpgradeStatus: Upgraded to saucy on 2013-07-05 (46 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 #1194465, 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.