VirtualBox crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
virtualbox (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Crash in VM power Actions
ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: virtualbox-qt 5.1.18-dfsg-1
ProcVersionSign
Uname: Linux 4.10.0-13-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: LXDE
Date: Wed Mar 22 09:06:47 2017
Disassembly: => 0x7f7c6d3ff55f: Não é possível acessar a memória no endereço 0x7f7c6d3ff55f
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2016-08-02 (231 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f7c6d3ff55f: Não é possível acessar a memória no endereço 0x7f7c6d3ff55f
PC (0x7f7c6d3ff55f) not located in a known VMA region (needed executable region)!
source "0x7f7c6d3ff55f" (0x7f7c6d3ff55f) not located in a known VMA region (needed readable region)!
Stack memory exhausted (SP below stack segment)
SegvReason:
executing unknown VMA
reading unknown VMA
Signal: 11
SourcePackage: virtualbox
StacktraceTop:
()
()
()
()
()
Title: VirtualBox crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf vboxusers
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()