ut2004-bin-linux-amd64 - regression?
ut2004-bin-linux-amd64 was previously working on RPI4 (Bullseye). Suddenly it started crashing (below). In case it matters, Raspberry Pi OS started pushing a new Mesa with Vulkan 1.2 support.
pi@pi:~/games/ut2004/System $ export SDL_VIDEODRIVER=wayland
pi@pi:~/games/ut2004/System $ export BOX86_PREFER_WRAPPED=1
pi@pi:~/games/ut2004/System $ ./ut2004-bin-linux-amd64
Dynarec for ARM64, with extension: ASIMD CRC32 PageSize:4096
Box64 with Dynarec v0.1.9 dc5c049 built on Aug 10 2022 06:44:11
Using default BOX64_LD_LIBRARY_PATH: ./:lib/:lib64/:x86_64/:bin64/:libs64/
BOX64: Prefer Wrapped libs
Using default BOX64_PATH: ./:bin/
Counted 57 Env var
Looking for ./ut2004-bin-linux-amd64
Rename process to "ut2004-bin-linux-amd64"
Using native(wrapped) libdl.so.2
Using native(wrapped) libc.so.6
Using native(wrapped) ld-linux-x86-64.so.2
Using native(wrapped) libpthread.so.0
Using native(wrapped) librt.so.1
Using native(wrapped) libSDL-1.2.so.0
Using native(wrapped) libm.so.6
Using emulated libstdc++.so.5
Using emulated /lib/x86_64-linux-gnu/libgcc_s.so.1
16212|SIGSEGV @0x6499cb14 (???(./ut2004-bin-linux-amd64+0x6499cb14)) (x64pc=0x6417c2//home/pi/games/ut2004/System/ut2004-bin-linux-amd64:"???", rsp=0x7f93c56b20, stack=0x7f9345b000:0x7f93c5b000 own=(nil) fp=0xa0608800), for accessing 0x13f266602 (code=1/prot=0), db=(nil)((nil):(nil)/(nil):(nil)/???:clean, hash:0/0) handler=0xb29b30
RSP-0x20:0x000000009c8b1510 RSP-0x18:0x0000007f93c57470 RSP-0x10:0x0000000000fb0230 RSP-0x08:0x0000000000641749
RSP+0x00:0x0000000000000000 RSP+0x08:0x0000000000000001 RSP+0x10:0x0000000000000000 RSP+0x18:0x00000000a0608800
Signal: SIGSEGV [segmentation fault]
Aborting.
Crash information will be saved to your logfile.
FillBlock at 0x533290 triggered a segfault, cancelling
In case it matters, Raspberry Pi OS started pushing a new Mesa with Vulkan 1.2 support.
@Roburetto this is incorrect. piOS (buster and bullseye) do not even have the vulkan 1.1 capable drivers STILL. the vulkan 1.2 capable drivers have been merged into mesa 22.X. piOS buster and bullseye are still using mesa 20.X with the vulkan 1.0 only capable drivers.
Can you re-try now, I have fixed an issue in the interpreter that might have cause the saugfault...
Started working again with: Box64 with Dynarec v0.1.9 d90b6b7 built on Aug 11 2022 06:42:12
As for the vulkan and mesa versions on Raspberry, I may have jumped into conclusions, once I got the below following a mesa update:
VULKANINFO Vulkan Instance Version: 1.2.162
Yeah you need to read from the correct place..
GPU0:
VkPhysicalDeviceProperties:
---------------------------
apiVersion = 4194459 (1.0.155)
driverVersion = 83898373 (0x5003005)
vendorID = 0x14e4
deviceID = 0x002a
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName = V3D 4.2
As I said, it is still 1.0 on PiOS