I have a 2019 iMac and a 2020 MacBook Pro, both with intel CPU, both running the latest OS Ventura 13.3.1. Both have a fedora 38 server virtual box guest. In fedora guest on iMac, running a program in gdb will get a segfault:
Program received signal SIGSEGV, Segmentation fault.
_dl_unload_cache () at dl-cache.c:525
Downloading source file /usr/src/debug/glibc-2.37-1.fc38.x86_64/elf/dl-cache.c
525 {
(gdb) where
#0 _dl_unload_cache () at dl-cache.c:525
#1 0x0000000000401048 in _start ()
The exact same thing on MacBook Pro runs fine. I even tried to create a brand new fedora guest on both the same way, install the same packages, still programs in gdb in fedora on iMac fails, while on MacBook Pro succeed.
Anyone know what could be the cause?
running program in gdb get segfault
-
- Volunteer
- Posts: 711
- Joined: 3. Mar 2015, 07:27
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Linux, macOS, Windows
Re: running program in gdb get segfault
What version(s) of VirtualBox are you running on the 2 hosts?
Re: running program in gdb get segfault
7.0.6 on both.
-
- Volunteer
- Posts: 711
- Joined: 3. Mar 2015, 07:27
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Linux, macOS, Windows
Re: running program in gdb get segfault
You could maybe try one of the current testbuilds of VirtualBox from https://www.virtualbox.org/wiki/Testbuilds
There were problems with Ventura13.3.1 because of changes in Apple's hypervisor engine. They appear to be fixed in the latest test builds.
Ignore the stuff about disabling SIP - that is not applicable to VirtualBox 7.x as kernel extensions (kexts) are no longer installed.
There were problems with Ventura13.3.1 because of changes in Apple's hypervisor engine. They appear to be fixed in the latest test builds.
Ignore the stuff about disabling SIP - that is not applicable to VirtualBox 7.x as kernel extensions (kexts) are no longer installed.