Project

General

Profile

Actions

Bug #8798

closed

VirtualBox 5.1.30 fails to start with segmentation fault

Added by r a over 4 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2017-11-11
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage

Description

Upgraded to Virtualbox 5.1.30 from VirtualBox 5.0.40, used the following instructions to install VirtualBox 5.1.30 successfully (rebooted after installation to ensure correct modules loaded)

$ pkgtrans VirtualBox-5.1.30-SunOS-amd64-r118389.pkg . all
$ rm SUNWvbox/install/checkinstall
$ sed -i /checkinstall/d SUNWvbox/pkgmap
$ pfexec pkgadd -d . SUNWvbox

When attempting to start VirtualBox 5.1.30 it fails with a "Segmentation Fault".
Performed a truss -leaf -o on VirtualBox, see results in attached file.
It appears that /opt/VirtualBox/amd64/VirtualBox is crashing.

$ ldd /opt/VirtualBox/amd64/VirtualBox
librt.so.1 => /lib/64/librt.so.1
libgcc_s.so.1 => /usr/lib/64/libgcc_s.so.1
libc.so.1 => /lib/64/libc.so.1
libm.so.2 => /lib/64/libm.so.2

When I attempt to truss /opt/VirtualBox/amd64/VirtualBox I get the following error

$ truss -leafo /tmp/russell /opt/VirtualBox/amd64/VirtualBox
truss: cannot trace set-id or unreadable object file: /opt/VirtualBox/amd64/VirtualBox

$ ls -l /opt/VirtualBox/amd64/VirtualBox
-rwsr-xr-x 1 root bin 162848 Oct 16 11:05 VirtualBox


Files

VirtualBox.truss (24.5 KB) VirtualBox.truss truss -leaf -o /tmp/VirtualBox.truss VirtualBox r a, 2017-11-11 02:51 PM
ldd_of_amd64 (52.9 KB) ldd_of_amd64 ldd /opt/VirtualBox/amd64/* r a, 2017-11-11 03:34 PM
Actions

Also available in: Atom PDF