VirtualBox crashed with SIGSEGV

[Derick Fynn]

   broken

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: virtualbox-qt 4.3.2-dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
ApportVersion: 2.13.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jan 27 01:27:31 2014
Disassembly: => 0x35: Cannot access memory at address 0x35
ExecutablePath: /usr/lib/virtualbox/VirtualBox
InstallationDate: Installed on 2013-03-23 (311 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
ProcCmdline: /usr/lib/virtualbox/VirtualBox --comment Windows7 --startvm 277231d8-8d6a-43c1-a7fc-ca8b31f01e02 --no-startvm-errormsgbox
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
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/virtualbox/VBoxXPCOM.so
 ?? () from /usr/lib/virtualbox/components/VBoxXPCOMIPCC.so
 ?? () from /usr/lib/virtualbox/VBoxXPCOM.so
 ?? () from /usr/lib/virtualbox/VBoxXPCOM.so
Title: VirtualBox crashed with SIGSEGV
UpgradeStatus: Upgraded to trusty on 2014-01-26 (1 days ago)
UserGroups:

[Apport retracing service (apport)]

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 #1273340, 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.