search

zesterer / openmw-volumetric-clouds

A volumetric clouds mod for OpenMW
86 stars 12 forks source link

Crashes on M1 MacBook #41

Open 20-h-thoreau opened 1 week ago

20-h-thoreau commented 1 week ago

I'm using the latest development build of OpenMW on Sonoma 14. After reading the previous issue and setting NO_BITWISE to 1, the shader compiled, but whenever the game boots or I turn the shader on, it immediately crashes the game. Crashlog is as follows:

*** Fatal Error ***
Invalid permissions for mapped object (signal 11)
Address: 0x0

Executing: gdb --pid 5874 --quiet --batch --command /tmp/gdb-script-lT6s3z

Failed to create a crash report.
Please make sure that 'gdb' is installed and present in PATH then crash again.
Current PATH: /usr/bin:/bin:/usr/sbin:/sbin
Executing: lldb --attach-pid 5874 --batch --source /tmp/lldb-script-vax0R5
(lldb) process attach --pid 5874
Process 5874 stopped
* thread #1, stop reason = signal SIGSTOP
    frame #0: 0xffffffffffffffff 
Target 0: (No executable module.) stopped.
Architecture set to: .
(lldb) command source -s 0 '/tmp/lldb-script-vax0R5'
Executing commands in '/tmp/lldb-script-vax0R5'.
(lldb) script print("\n* Loaded Libraries")

* Loaded Libraries
(lldb) image list

Failed to create a crash report.
Please make sure that 'lldb' is installed and present in PATH then crash again.
Current PATH: /usr/bin:/bin:/usr/sbin:/sbin

Likewise, lldb says:

Process 6190 stopped
* thread #39, stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
    frame #0: 0x00000001f1cc457c libGLProgrammability.dylib`glpLLVMGetFunctionGlobalVariableUse + 116
libGLProgrammability.dylib`glpLLVMGetFunctionGlobalVariableUse:
->  0x1f1cc457c <+116>: ldr    x1, [x23]
    0x1f1cc4580 <+120>: mov    x0, x20
    0x1f1cc4584 <+124>: bl     0x1f1cc5288               ; glpLLVMAddSortedParameters
    0x1f1cc4588 <+128>: ldr    w8, [x23, #0x8]

Admittedly I'm not very experienced with gdb/lldb so I don't know enough to find out much more but I'm happy to try any commands someone might suggest. Thank you for your time.

Minor update: I just tried the version from April 3rd with the code modified (as per the issue) and it works. Later I will try out later versions as well to see which one broke it.