[Can't reproduce] [Linux, Blood, Release] Segfault when entering another level

Moderator: Raze Developers

[Linux, Blood, Release] Segfault when entering another level

Postby Talon1024 » Sun Feb 09, 2020 12:11 am

On some of the games I've tested with Raze, I get a segmentation fault as I enter the next level.

Duke Nukem 3D is not affected, but Blood is, and Shadow Warrior also became affected by this issue after this commit. I haven't tested NAM, and I don't have WW2GI, Redneck Rampage, or Powerslave/Exhumed.
Last edited by Talon1024 on Sun Feb 09, 2020 8:08 pm, edited 1 time in total.
Talon1024
 
 
 
Joined: 28 Jun 2016
Github ID: Talon1024
Operating System: Debian-like Linux (Debian, Ubuntu, Kali, Mint, etc) 64-bit
Graphics Processor: nVidia with Vulkan support

Re: [Linux] Segfaults when entering another level

Postby Graf Zahl » Sun Feb 09, 2020 1:16 am

Please post a crash log. I cannot investigate "a segmentation fault" with no data.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
 
Joined: 19 Jul 2003
Location: Germany

Re: [Linux] Segfaults when entering another level

Postby Talon1024 » Sun Feb 09, 2020 1:58 am

I don't get much of a crash log. The last few lines in the terminal are:
Code: Select allExpand view
> Modern types erased: 0.
> This map *does not* provides modern features.
[1]    15605 segmentation fault (core dumped)  ~/Games/code/Raze/build/raze


This is from Blood, going from E1L1 to E1L2.
Talon1024
 
 
 
Joined: 28 Jun 2016
Github ID: Talon1024
Operating System: Debian-like Linux (Debian, Ubuntu, Kali, Mint, etc) 64-bit
Graphics Processor: nVidia with Vulkan support

Re: [Linux] Segfaults when entering another level

Postby _mental_ » Sun Feb 09, 2020 2:09 am

Run Raze under GDB or LLDB then. Also, the function changed in that commit is called only when playing Shadow Warrior.
_mental_
 
 
 
Joined: 07 Aug 2011

Re: [Linux] Segfaults when entering another level

Postby Graf Zahl » Sun Feb 09, 2020 2:14 am

Going from E1M1 to E1M2 does not crash for me under Windows.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
 
Joined: 19 Jul 2003
Location: Germany

Re: [Linux] Segfaults when entering another level

Postby Talon1024 » Sun Feb 09, 2020 12:57 pm

Now that the debug build works for me, I found that I was able to proceed from E1L1 to E1L2 without issues. But, the release build crashes. This is the backtrace from GDB:
Code: Select allExpand view
#0  0x0000555555983c16 in Blood::CalcGameChecksum() ()
#1  0x000055555594a435 in Blood::ProcessFrame() ()
#2  0x000055555594acc0 in Blood::GameInterface::app_main() ()
#3  0x0000555555799996 in RunGame() ()
#4  0x000055555579ad5b in GameMain() ()
#5  0x00005555556ef992 in main ()
Talon1024
 
 
 
Joined: 28 Jun 2016
Github ID: Talon1024
Operating System: Debian-like Linux (Debian, Ubuntu, Kali, Mint, etc) 64-bit
Graphics Processor: nVidia with Vulkan support

Re: [Linux, Blood, Release] Segfault when entering another l

Postby Cacodemon345 » Sun Mar 01, 2020 1:35 pm

In which line does that happen?

This isn't very informative and useful for fixing the crash.
Cacodemon345
 
Joined: 22 Dec 2017
Discord: Cacodemon345#9151
Github ID: Cacodemon345
Operating System: Windows 10/8.1/8/201x 64-bit
Graphics Processor: ATI/AMD (Modern GZDoom)

Re: [Linux, Blood, Release] Segfault when entering another l

Postby Graf Zahl » Sun Mar 01, 2020 1:53 pm

No, it isn't. I cannot see how that code can even crash.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
 
Joined: 19 Jul 2003
Location: Germany

Re: [Linux, Blood, Release] Segfault when entering another l

Postby mjr4077au » Mon Sep 21, 2020 5:12 pm

I can't replicate this on the current master with an up-to-date Arch Linux. Given the age of the issue and that it pre-dates the release of 0.6.0 in April, I'll close for now but please report if it's still occurring.
User avatar
mjr4077au
 
Joined: 17 Jun 2019
Location: Gosford NSW, Australia
Discord: mjr4077au#1027
Github ID: mjr4077au
Operating System: Windows 10/8.1/8/201x 64-bit
OS Test Version: No (Using Stable Public Version)
Graphics Processor: nVidia with Vulkan support


Return to Closed Bugs

Who is online

Users browsing this forum: No registered users and 0 guests