VirtualBox crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
virtualbox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Virtualbox crash when removing image from virtual drive.
Distributor ID: Ubuntu
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
Codename: trusty
virtualbox:
Installed: 4.3.6-dfsg-2
Candidate: 4.3.6-dfsg-2
Version table:
*** 4.3.6-dfsg-2 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: virtualbox-qt 4.3.6-dfsg-2
Uname: Linux 3.13.3-
NonfreeKernelMo
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Tue Mar 18 14:24:02 2014
Disassembly: => 0x35: Cannot access memory at address 0x35
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2014-03-17 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140317)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x35: Cannot access memory at address 0x35
PC (0x00000035) not located in a known VMA region (needed executable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: virtualbox
StacktraceTop:
?? ()
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: VirtualBox crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
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 #1289709, 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.