Segfault Of VirtualBox-5.0 On CentOS5 System

[hoeferbe]

I have a CentOS 5.11 x86_64 server upon which I've been running previous VirtualBox versions. (CentOS is a RHEL clone, so this would be the equivalent of RHEL 5.11). This server is dual-headed (from the same ATI Radeon HD2600 card) and has 3D acceleration enabled via the AMD/ATI Catalyst 13.1 proprietary driver.

I recently removed VirtualBox 4.3 ("yum remove VirtualBox-4.3.x86_64") and installed VirtualBox 5.0 ("yum install VirtualBox-5.0.x86_64", which installed VirtualBox-5.0-5.0.0_101573_el5-1.x86_64). Both operations executed successfully, with new kernel modules being built for 5.0.

However, when I try to execute the VirtualBox program, it segfaults:

[user@server ~]$ VirtualBox Segmentation fault

[user@server ~]$ sudo tail -n1 /var/log/messages Jul 22 08:13:48 server kernel: VirtualBox[3967]: segfault at 0000000000000000 rip 00002b4a8d1cd3ff rsp 00007fff977bfc70 error 4

Nothing is written to the log files in $HOME/.VirtualBox.

I didn't see anything in the forums about this, but there is a similar issue described in ticket #14278 for VirtualBox 5.0 on RHEL 6.4.

Thinking there might be something new with VirtualBox 5.0, I read through the installation sections of the user guide. Although I do not think this is the problem, I noted from chapter 2.3 that I do not have the required version of Qt 4.8.0 or higher; I have qt-3.3.6-26.el5.x86_64, which is the version that comes with CentOS/RHEL 5. If that really is required, then I'd like to recommend either the documentation be changed to state that one will need to get that package from a 3rd-party repository or remove CentOS/RHEL 5 from the supported host operating systems list.

I will upload the core file to this ticket. Thank you for your assistance with this issue and all the great work that goes into the VirtualBox product!

[hoeferbe]

Since <https://www.virtualbox.org/wiki/Core_dump> states that core files can include sensitive information, I tried uploading the core file to ftp.oracle.com, but it is not available:

[user@server ~]$ ftp -ni ftp.oracle.com
Connected to ftp.oracle.com (141.146.1.166).
421 Service not available, remote server has closed connection

That wiki document also lists an e-mail address for Frank Mehnert to which one could e-mail the core file. Yet, not knowing who that is, I'm instead seeking direction from whoever is assigned to this ticket on how to get this core file to Oracle confidentially. My compressed core file (core.3967_ForVirtualBoxTicket14315.gz) is 508 kB big. Thank you again.

[hoeferbe]

Replying to hoeferbe:
===

I didn't see anything in the forums about this, but there is a similar issue described in ticket #14278 for VirtualBox 5.0 on RHEL 6.4.

===

I noted from chapter 2.3 that I do not have the required version of Qt 4.8.0 or higher; I have qt-3.3.6-26.el5.x86_64, which is the version that comes with CentOS/RHEL 5.

===

Looking again a ticket #14278, I see his segfault output includes more that mine; it states the segfault was in libQtCoreVBox.so.4. So maybe mine (and his) problems stem from not having the minimal QT version? (His problem is on RHEL 6.4, thus he is likely using qt-4.6.2...)

[hoeferbe]

FYI, I was able to uninstall v.5.0 ("yum remove VirtualBox-5.0.x86_64"), install v.4.3 ("yum install VirtualBox-4.3.x86_64", which installed VirtualBox-4.3-4.3.30_101610_el5-1.x86_64) and it is fine.

[Frank Mehnert]

Please attach a VBox.log file of a 5.0 session. And having a core dump from a crashing session would be even better.

[hoeferbe]

Replying to frank:
===

Please attach a VBox.log file of a 5.0 session.

===

As I stated in my opening comment, *no* log files are written to $HOME/.VirtualBox; the application segfaults before it even gets to the point of writing logs.

===

And having a core dump from a crashing session would be even better.

===

My comment #2 states I have a core dump but the FTP site was not working (and it still is not; I just tried) and I didn't know who "Frank" was. I take it you are Frank Mehnert? I will go ahead and e-mail it to you. (Again, it is 508 kB after gzip compression.) Thank you!

[Frank Mehnert]

Thanks for the core dump. So far I can only see that the crash happens inside a Qt library. Is there a DISPLAY variable defined when you try to start VirtualBox?

Also, could you try this test build? I doubt it will make any difference for you but the core dump should contain a few more information.

[hoeferbe]

Replying to frank:
===

Thanks for the core dump. So far I can only see that the crash happens inside a Qt library. Is there a DISPLAY variable defined when you try to start VirtualBox?

===

Yes, there is a DISPLAY variable defined:

[user@server ~]$ echo $DISPLAY
:0.0

Since you mention it crashing inside a Qt library, I'd just like to remind you that I have qt-3.3.6-26.el5.x86_64, which is the version that comes with CentOS/RHEL 5. According to chapter 2.3.1 of the user manual, I do not have the required version of Qt 4.8.0 or higher.

I just noticed the note in the green box on that user manual page; is it new? It states that I could run VBoxSDL or VBoxHeadless to avoid using Qt. I don't have time to try that right now, but should be able to on Sunday.

===

Also, could you try this test build? I doubt it will make any difference for you but the core dump should contain a few more information.

===

Same result; I will e-mail you a gzipped copy of the new core dump. Again, nothing was logged to $HOME/.VirtualBox or $HOME/VirtualBox VMs.

[user@server ~]$ echo -n 1 | sudo tee /proc/sys/fs/suid_dumpable
1

[user@server ~]$ ulimit -c unlimited

[user@server ~]$ echo -n 1 | sudo tee /proc/sys/kernel/core_uses_pid
1

[user@server ~]$ VirtualBox
Segmentation fault (core dumped)

[user@server ~]$ ll -ta | head
total 1328776
drwx------ 21 user user       4096 Aug  6 23:38 .
-rw-------  1 user user   13934592 Aug  6 23:38 core.16748

[user@server ~]$ sudo tail -n1 /var/log/messages
Aug  6 23:38:28 server kernel: VirtualBox[16748]: segfault at 0000000000000000 rip 00002ac33f29e3ff rsp 00007fff9d752c00 error 4

[Frank Mehnert]

Thanks again for the core dump. I see where the code crashes but I don't know why. Could you also add the output of

ldd -r /usr/lib/virtualbox/VirtualBox.so

? It should not matter which Qt version you have installed on your system because the .rpm package contains Qt 4.8.6.

It could also make sense to install the Linux .run installer from the download page instead of the el5 package to see if there is a difference.

[Frank Mehnert]

Any improvement with VBox 5.0.2? If not, could you provide the information I asked in the previous comment? Thank you!

[hoeferbe]

Replying to frank:
===

Thanks again for the core dump.

===

Thank you for your patience. I am sorry it takes me awhile to get back with you.

===

Could you also add the output of

ldd -r /usr/lib/virtualbox/VirtualBox.so

?

===

Sure. Here it is:

[root@server ~]# ldd -r /usr/lib/virtualbox/VirtualBox.so
	linux-vdso.so.1 =>  (0x00007fff94bb4000)
	libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00002ba9ed252000)
	libGL.so.1 => /usr/lib64/libGL.so.1 (0x00002ba9ed455000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00002ba9ed65e000)
	VBoxKeyboard.so => /usr/lib/virtualbox/VBoxKeyboard.so (0x00002ba9ed862000)
	VBoxRT.so => /usr/lib/virtualbox/VBoxRT.so (0x00002ba9eda74000)
	libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00002ba9ededa000)
	libXext.so.6 => /usr/lib64/libXext.so.6 (0x00002ba9ee0e4000)
	libX11.so.6 => /usr/lib64/libX11.so.6 (0x00002ba9ee2f6000)
	VBoxXPCOM.so => /usr/lib/virtualbox/VBoxXPCOM.so (0x00002ba9ee602000)
	libQtCoreVBox.so.4 => /usr/lib/virtualbox/libQtCoreVBox.so.4 (0x00002ba9ee921000)
	libQtGuiVBox.so.4 => /usr/lib/virtualbox/libQtGuiVBox.so.4 (0x00002ba9eeda1000)
	libQtNetworkVBox.so.4 => /usr/lib/virtualbox/libQtNetworkVBox.so.4 (0x00002ba9efb4d000)
	libQtOpenGLVBox.so.4 => /usr/lib/virtualbox/libQtOpenGLVBox.so.4 (0x00002ba9efd97000)
	libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00002ba9effb5000)
	libm.so.6 => /lib64/libm.so.6 (0x00002ba9f02b5000)
	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002ba9f0538000)
	libc.so.6 => /lib64/libc.so.6 (0x00002ba9f0747000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00002ba9f0aa0000)
	/lib64/ld-linux-x86-64.so.2 (0x00000030dc200000)
	libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00002ba9f0cbc000)
	libz.so.1 => /lib64/libz.so.1 (0x00002ba9f0ef5000)
	librt.so.1 => /lib64/librt.so.1 (0x00002ba9f1109000)
	libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00002ba9f1312000)
	libssl.so.6 => /lib64/libssl.so.6 (0x00002ba9f1651000)
	libcrypto.so.6 => /lib64/libcrypto.so.6 (0x00002ba9f189f000)
	libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00002ba9f1bf1000)
	libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00002ba9f1dfb000)
	libXau.so.6 => /usr/lib64/libXau.so.6 (0x00002ba9f2000000)
	libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00002ba9f2202000)
	libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00002ba9f2408000)
	libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x00002ba9f263c000)
	libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00002ba9f2840000)
	libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00002ba9f2adf000)
	libSM.so.6 => /usr/lib64/libSM.so.6 (0x00002ba9f2d63000)
	libICE.so.6 => /usr/lib64/libICE.so.6 (0x00002ba9f2f6d000)
	libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00002ba9f3189000)
	libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00002ba9f33b7000)
	libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00002ba9f364d000)
	libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00002ba9f384f000)
	libexpat.so.0 => /lib64/libexpat.so.0 (0x00002ba9f3a74000)
	libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00002ba9f3c98000)
	libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00002ba9f3ea0000)
	libresolv.so.2 => /lib64/libresolv.so.2 (0x00002ba9f40a2000)
	libselinux.so.1 => /lib64/libselinux.so.1 (0x00002ba9f42b8000)
	libsepol.so.1 => /lib64/libsepol.so.1 (0x00002ba9f44d0000)

===

It should not matter which Qt version you have installed on your system because the .rpm package contains Qt 4.8.6.

===

Oh, OK. I did not know the VirtualBox RPM file satisfied that requirement. Thank you for explaining that.

===

It could also make sense to install the Linux .run installer from the download page instead of the el5 package to see if there is a difference.

===

I can do that if you really want, but on my servers I avoid non-RPM installs so that everything is know about & controlled via the package manager.

Replying to frank:
===

Any improvement with VBox 5.0.2?

===

Unfortunately, no. Do you want this latest core file, too?

[root@server ~]# rpm -e VirtualBox-4.3-4.3.30_101610_el5-1.x86_64

[root@server ~]# yum -y install VirtualBox-5.0
...
=================================================================
 Package          Arch     Version              Repository   Size
=================================================================
Installing:
 VirtualBox-5.0   x86_64   5.0.2_102096_el5-1   virtualbox   81 M
Transaction Summary
=================================================================
Install       1 Package(s)
Upgrade       0 Package(s)
Total download size: 81 M
...
Creating group 'vboxusers'. VM users must be member of that group!
No precompiled module for this kernel found -- trying to build one. Messages
emitted during module compilation will be logged to /var/log/vbox-install.log.
Stopping VirtualBox kernel modules [  OK  ]
Recompiling VirtualBox kernel modules [  OK  ]
Starting VirtualBox kernel modules [  OK  ]
Installed:
  VirtualBox-5.0.x86_64 0:5.0.2_102096_el5-1
Complete!

[root@server ~]# shutdown -r now
Broadcast message from root (pts/0) (Mon Aug 17 07:05:39 2015):
The system is going down for reboot NOW!

[user@server ~]$ rpm -q VirtualBox-5.0
VirtualBox-5.0-5.0.2_102096_el5-1.x86_64

[user@server ~]$ echo -n 1 | sudo tee /proc/sys/fs/suid_dumpable 
1

[user@server ~]$ ulimit -c unlimited

[user@server ~]$ echo -n 1 | sudo tee /proc/sys/kernel/core_uses_pid 
1

[user@server ~]$ VirtualBox 
Segmentation fault (core dumped)

[user@server ~]$ ll -tgo | head -n3
total 1328780
drwx------ 21      4096 Aug 17 07:11 .
-rw-------  1  13934592 Aug 17 07:11 core.3853

[user@server ~]$ sudo tail -n1 /var/log/messages
Aug 17 07:11:37 server kernel: VirtualBox[3853]: segfault at 0000000000000000 rip 00002b27ce6ea3ff rsp 00007ffff5abb140 error 4

[hoeferbe]

Replying to hoeferbe:
===

Replying to frank:
===

Could you also add the output of

ldd -r /usr/lib/virtualbox/VirtualBox.so

?

===

Sure. Here it is:

===

Oops, that was the output when I still had VirtualBox-4.3 installed. Here is the output after installing VirtualBox-5.0-5.0.2_102096_el5-1.x86_64.

	linux-vdso.so.1 =>  (0x00007fffbf5fd000)
	libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00002b3e93468000)
	libGL.so.1 => /usr/lib64/libGL.so.1 (0x00002b3e9366b000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00002b3e93874000)
	VBoxKeyboard.so => /usr/lib/virtualbox/VBoxKeyboard.so (0x00002b3e93a78000)
	VBoxRT.so => /usr/lib/virtualbox/VBoxRT.so (0x00002b3e93c8a000)
	libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00002b3e940f7000)
	libXext.so.6 => /usr/lib64/libXext.so.6 (0x00002b3e94301000)
	libX11.so.6 => /usr/lib64/libX11.so.6 (0x00002b3e94513000)
	VBoxXPCOM.so => /usr/lib/virtualbox/VBoxXPCOM.so (0x00002b3e9481f000)
	libQtCoreVBox.so.4 => /usr/lib/virtualbox/libQtCoreVBox.so.4 (0x00002b3e94b3f000)
	libQtGuiVBox.so.4 => /usr/lib/virtualbox/libQtGuiVBox.so.4 (0x00002b3e950c9000)
	libQtNetworkVBox.so.4 => /usr/lib/virtualbox/libQtNetworkVBox.so.4 (0x00002b3e95e12000)
	libQtOpenGLVBox.so.4 => /usr/lib/virtualbox/libQtOpenGLVBox.so.4 (0x00002b3e96140000)
	libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00002b3e9644c000)
	libm.so.6 => /lib64/libm.so.6 (0x00002b3e9674c000)
	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002b3e969cf000)
	libc.so.6 => /lib64/libc.so.6 (0x00002b3e96bde000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00002b3e96f37000)
	/lib64/ld-linux-x86-64.so.2 (0x00000030dc200000)
	libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00002b3e97153000)
	libz.so.1 => /lib64/libz.so.1 (0x00002b3e9738c000)
	librt.so.1 => /lib64/librt.so.1 (0x00002b3e975a0000)
	libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00002b3e977a9000)
	libssl.so.6 => /lib64/libssl.so.6 (0x00002b3e97ae8000)
	libcrypto.so.6 => /lib64/libcrypto.so.6 (0x00002b3e97d36000)
	libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00002b3e98088000)
	libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00002b3e98292000)
	libXau.so.6 => /usr/lib64/libXau.so.6 (0x00002b3e98497000)
	libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00002b3e98699000)
	libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00002b3e9889f000)
	libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x00002b3e98ad3000)
	libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00002b3e98cd7000)
	libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00002b3e98f76000)
	libSM.so.6 => /usr/lib64/libSM.so.6 (0x00002b3e991fa000)
	libICE.so.6 => /usr/lib64/libICE.so.6 (0x00002b3e99404000)
	libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00002b3e99620000)
	libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00002b3e9984e000)
	libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00002b3e99ae4000)
	libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00002b3e99ce6000)
	libexpat.so.0 => /lib64/libexpat.so.0 (0x00002b3e99f0b000)
	libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00002b3e9a12f000)
	libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00002b3e9a337000)
	libresolv.so.2 => /lib64/libresolv.so.2 (0x00002b3e9a539000)
	libselinux.so.1 => /lib64/libselinux.so.1 (0x00002b3e9a74f000)
	libsepol.so.1 => /lib64/libsepol.so.1 (0x00002b3e9a967000)

[hoeferbe]

Tonight, I tried using VirtualBox-5.0-5.0.10_104061_el5-1.x86_64 on my CentOS5.11 machine and I again got the segmentation fault. The error displayed in /var/log/messages is slightly different than before; it now has a "SUPROGipMap" line:

Nov 22 17:08:27 server kernel: SUPR0GipMap: fGetGipCpu=0x3
Nov 22 17:08:28 server kernel: VirtualBox[3933]: segfault at 0000000000000000 rip 00002ae0f90dc3ff rsp 00007fff928d18e0 error 4

The output of "ldd -r /usr/lib/virtualbox/VirtualBox.so" is below. The 14MB core I captured -- core.3933, whose MD5 hash is e4b8ff6371d14ed3b481ca022366b061 -- will be gzipped and e-mailed.

Thanks again for looking into this.

linux-vdso.so.1 =>  (0x00007fff14f96000)
libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00002b3cb1028000)
libGL.so.1 => /usr/lib64/libGL.so.1 (0x00002b3cb122b000)
libdl.so.2 => /lib64/libdl.so.2 (0x00002b3cb1434000)
VBoxKeyboard.so => /usr/lib/virtualbox/VBoxKeyboard.so (0x00002b3cb1638000)
VBoxRT.so => /usr/lib/virtualbox/VBoxRT.so (0x00002b3cb184a000)
libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00002b3cb1cc2000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00002b3cb1ecc000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00002b3cb20de000)
VBoxXPCOM.so => /usr/lib/virtualbox/VBoxXPCOM.so (0x00002b3cb23ea000)
libQtCoreVBox.so.4 => /usr/lib/virtualbox/libQtCoreVBox.so.4 (0x00002b3cb270a000)
libQtGuiVBox.so.4 => /usr/lib/virtualbox/libQtGuiVBox.so.4 (0x00002b3cb2c94000)
libQtOpenGLVBox.so.4 => /usr/lib/virtualbox/libQtOpenGLVBox.so.4 (0x00002b3cb39dd000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00002b3cb3ce8000)
libm.so.6 => /lib64/libm.so.6 (0x00002b3cb3fe9000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002b3cb426c000)
libc.so.6 => /lib64/libc.so.6 (0x00002b3cb447a000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00002b3cb47d4000)
/lib64/ld-linux-x86-64.so.2 (0x00002b3cb0266000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00002b3cb49f0000)
libz.so.1 => /lib64/libz.so.1 (0x00002b3cb4c28000)
librt.so.1 => /lib64/librt.so.1 (0x00002b3cb4e3d000)
libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00002b3cb5046000)
libssl.so.6 => /lib64/libssl.so.6 (0x00002b3cb5384000)
libcrypto.so.6 => /lib64/libcrypto.so.6 (0x00002b3cb55d3000)
libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00002b3cb5925000)
libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00002b3cb5b2e000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00002b3cb5d34000)
libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00002b3cb5f36000)
libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00002b3cb613b000)
libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x00002b3cb6370000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00002b3cb6574000)
libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00002b3cb6812000)
libSM.so.6 => /usr/lib64/libSM.so.6 (0x00002b3cb6a97000)
libICE.so.6 => /usr/lib64/libICE.so.6 (0x00002b3cb6ca1000)
libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00002b3cb6ebd000)
libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00002b3cb70eb000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00002b3cb7380000)
libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00002b3cb7583000)
libexpat.so.0 => /lib64/libexpat.so.0 (0x00002b3cb77a8000)
libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00002b3cb79cc000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00002b3cb7bd4000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00002b3cb7dd6000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00002b3cb7fec000)
libsepol.so.1 => /lib64/libsepol.so.1 (0x00002b3cb8204000)

[Frank Mehnert]

Thank you for the core dump and for showing the ouput of 'ldd -r'. The latter looks right.

Regarding your core dump: We crash in Qt when accessing some thread-local memory:

#ifdef HAVE_TLS
static __thread QThreadData *currentThreadData = 0;
#endif


...
// Utility functions for getting, setting and clearing thread specific data.
static QThreadData *get_thread_data()
{
#ifdef HAVE_TLS
    return currentThreadData;
    ^^^^^^^^^^^^^^^^^^^^^^^^^
#else
    pthread_once(&current_thread_data_once, create_current_thread_data_key);
    return reinterpret_cast<QThreadData *>(pthread_getspecific(current_thread_data_key));
#endif
}

The glibc function __tls_get_addr() return NULL. Sounds to me like a glibc bug. Which version of glibc do you have installed (rpm -q glibc)?

[hoeferbe]

Thank you for your analysis, Frank.

Replying to frank:
===

Which version of glibc do you have installed (rpm -q glibc)?

===

I have the most up-do-date that comes with CentOS5 / RHEL5:

# rpm -q glibc
glibc-2.5-123.el5_11.3.x86_64
glibc-2.5-123.el5_11.3.i686

[Frank Mehnert]

Same here. I don't have a physical system but running the EL5 package within a CentOS 5 guest works without any problems. I have the same glibc libs installed.

Could you try the following:

$ sudo -s
$ yum install strace
$ strace -f -s128 -o log /usr/lib/virtualbox/VirtualBox

and attach the resulting log file to this ticket? I'm desperate but perhaps the strace log shows something interesting.

[Timothy Lee]

I'm running VirtualBox-5.0.12 on an up-to-date CentOS 5, and encounters the Segmentation Fault problem. I am able to run VBoxHeadless without triggering the crash.

I've attached a copy of the strace output as requested.

[hoeferbe]

Replying to frank:
===

Could you try the following:

> $ strace -f -s128 -o log /usr/lib/virtualbox/VirtualBox

===

I just installed and tried the VirtualBox-5.0-5.0.14_105127_el5-1.x86_64 RPM. Same issue as before. I am attaching requested strace (run by the root user). Thanks again!

[hoeferbe]

Strace from running VirtualBox-5.0-5.0.14_105127_el5-1.x86_64 on CentOS 5.11 with all updates as of 2016-01-24.

[Frank Mehnert]

Unfortunately I'm still not able to reproduce this problem with a test VM which runs CentOS 5. Thanks for providing the strace log files but they don't sched light into this problem. Everything seems to be normal at startup until the application crashes with SIGSEGV. I fear that we can't do anything as long as we cannot reproduce the problem, sorry. As written above, installing the universal .run package could be an alternative and is worth to try.