ZDoom / Raze

Build engine port backed by GZDoom tech. Currently supports Duke Nukem 3D, Blood, Shadow Warrior, Redneck Rampage and Powerslave/Exhumed.
664 stars 59 forks source link

[BUG] [Duke 3D] "Very fatal error" when trying to play user map #1063

Closed axredneck closed 5 months ago

axredneck commented 5 months ago

Raze version

Tried both 1.9.1 and commit g48977265a, both are from AUR. Edit: also tried "Linux Portable" build from Github (deleted it's libc.so.6 because else it doesn't run at all), and it gives the same "fatal error".

Which game are you running with Raze?

Duke Nukem 3D

What Operating System are you using?

Linux x86_64

Please describe your specific OS version

Arch Linux

Relevant hardware info

Ryzen 5 2600, Geforce GTX 1050, 32Gb RAM

Have you checked that no other similar issue already exists?

A clear and concise description of what the bug is.

That's it: Raze crashes when i try to play a user map Also i think it's a regression because i successfully played user maps in Raze a few months ago.

Steps to reproduce the behaviour.

Explain how to reproduce

  1. Select Duke Nukem 3D in Start Window
  2. Select "New Game", then "User Map"

Your configuration

Default config

Provide a Log

raze.log

And a window with this error appears

madame-rachelle commented 5 months ago

Try and rm the libc.so.6 from the raze-linux-portable folder does that fix the glibc errors?

axredneck commented 5 months ago

@madame-rachelle i already tried, see above.

coelckers commented 5 months ago

It doesn't crash on Windows so at the very least I need a crash log with symbols.

axredneck commented 5 months ago

@coelckers How can i get these symbols?

axredneck commented 5 months ago

Edit: i built raze-git from AUR with CMAKE_BUILD_TYPE=Debug, now it crashes immediately (no need to try to run user maps), here is raze-crash.log

axredneck commented 5 months ago

Meanwhile Windows version (under Wine) doesn't crash so i'll stick to it for now.

coelckers commented 5 months ago

I think this all sounds related to the filename case sensitivity bug with loaded directory content.