Workaround for gbd for crash reports macOS

Support for running, installing or compiling OpenMW

Before you submit a bug report for the first time, please read: Bug reporting guidelines
Post Reply
Stilllearningmonkey
Posts: 5
Joined: 30 Nov 2024, 06:10

Workaround for gbd for crash reports macOS

Post by Stilllearningmonkey »

I get an unspecified fatal error when loading a game. Crash log says I need gbd in order to get an actual detailed crash report. I can’t seem to figure out a way to get gbd installed as I am running a silicon Mac, macOS 15.1.1, openmw .48. Doesn’t seem like gbd is compatible with non-intel macs.
Is there a workaround that will allow me to get a crash report? Thanks
User avatar
psi29a
Posts: 5384
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: Workaround for gbd for crash reports macOS

Post by psi29a »

You can always post what's in your log file here. Might be something juicy in there and talk about what you were doing and if you can reproduce.

I was able to install gdb via brew on my M1; but not sure if that's enough.
Stilllearningmonkey
Posts: 5
Joined: 30 Nov 2024, 06:10

Re: Workaround for gbd for crash reports macOS

Post by Stilllearningmonkey »

Thanks for responding. I created a new post with the log info, also below:

[20:09:23.208 E] Cell reference 'dark_128' not found!
[20:09:23.208 E] Cell reference 'dark_128' not found!
[20:09:23.208 E] Cell reference 'dark_128' not found!
[20:09:23.208 E] Cell reference 'dark_128' not found!
[20:09:23.231 E] Cell reference 'dark_512_01' not found!
[20:09:23.232 E] Cell reference 'dark_512_01' not found!
[20:09:23.232 E] Cell reference 'dark_512_01' not found!
[20:09:23.262 E] Cell reference 'dark_512_01' not found!
[20:09:23.295 E] Cell reference 'dark_128' not found!
[20:09:23.295 E] Cell reference 'dark_128' not found!
[20:09:23.295 E] Cell reference 'dark_128' not found!
[20:09:23.295 E] Cell reference 'dark_128' not found!
[20:09:23.301 E] Cell reference 'dark_512_01' not found!
[20:09:23.303 W] PNG lib warning : iCCP: known incorrect sRGB profile
[20:09:23.506 I] Changing to interior
[20:09:23.506 I] Loading cell Imperial Prison Ship
[20:09:23.527 W] PNG lib warning : iCCP: known incorrect sRGB profile
[20:09:23.738 W] Scaling image 'splash/23 warrior ii.png' from (3840,2160) to (4096,2048)
[20:09:24.452 V] Fallback locale: en
[20:09:24.452 V] Language file "l10n/Navigation/en.yaml" is enabled
[20:10:23.351 W] FRAGMENT glCompileShader "main" FAILED
[20:10:23.351 W] FRAGMENT Shader "main" infolog:
[20:10:23.351 W] ERROR: 0:335: 'u' : syntax error: syntax error
[20:10:23.351 W]
[20:10:23.351 W] glLinkProgram 0x600010d6ec10"clouds" FAILED
[20:10:23.351 W] Program "clouds" infolog:
[20:10:23.351 W] ERROR: One or more attached shaders not successfully compiled
User avatar
psi29a
Posts: 5384
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: Workaround for gbd for crash reports macOS

Post by psi29a »

Can you narrow down which mod is causing this? You can disable that and should be good to go, but let us know so we can validate as well and create an issue from it. :)
LoneWolf
Posts: 149
Joined: 26 Sep 2017, 19:13

Re: Workaround for gbd for crash reports macOS

Post by LoneWolf »

The error looks very similar to the one I had a few weeks ago which turned out to be a mesa bug.

See https://gitlab.com/OpenMW/openmw/-/issues/8218 and https://gitlab.freedesktop.org/mesa/mesa/-/issues/12115.

Which mesa version are you using ?
User avatar
AnyOldName3
Posts: 2766
Joined: 26 Nov 2015, 03:25

Re: Workaround for gbd for crash reports macOS

Post by AnyOldName3 »

They're on MacOS, which is basically a walking OpenGL driver bug. It doesn't use Mesa, it uses Apple's homemade OpenGL driver. A post-process shader not compiling shouldn't cause a crash, though, so the messages about that shouldn't be relevant.
LoneWolf
Posts: 149
Joined: 26 Sep 2017, 19:13

Re: Workaround for gbd for crash reports macOS

Post by LoneWolf »

I agree failing a post-processing shader shouldn't crash the game.

Code: Select all

[20:10:23.351 W] glLinkProgram 0x600010d6ec10"clouds" FAILED
suggests the issue may not be with a specfiic shader, but with shader support in general.

@Stilllearningmonkey :
what are you using to provide OpenGL to openmw ?
If zink + moltenVK, which versions ?
User avatar
AnyOldName3
Posts: 2766
Joined: 26 Nov 2015, 03:25

Re: Workaround for gbd for crash reports macOS

Post by AnyOldName3 »

They'll be using MacOS's built-in terrible OpenGL support.
Post Reply