GZDoom 3.6.0 fatal crash ()

Bugs that have been investigated and resolved somehow.

Moderator: GZDoom Developers

Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
Post Reply
User avatar
Dinosaur_Nerd
Posts: 253
Joined: Wed Feb 21, 2018 5:31 pm
Operating System Version (Optional): Windows 10
Graphics Processor: nVidia (Modern GZDoom)
Location: timelocked USA 1994
Contact:

GZDoom 3.6.0 fatal crash ()

Post by Dinosaur_Nerd »

When creating a ZScript monster, setting a frame like this

Code: Select all

Pain:
        FATT J 4 ();                                // This frame causes GZDoom to crash
        FATT J 4 A_Pain();
        Goto See;
Causes GZDoom to crash with a very fatal error code : C0000005

I had to track down the problem manually and correct it.
I understand that this is a newbie mistake, however, I wasn't expecting GZDoom to crash to an error code and not give me a hint about what went wrong.

A test wad is available here: Broken Fatty
User avatar
Player701
 
 
Posts: 1640
Joined: Wed May 13, 2009 3:15 am
Graphics Processor: nVidia with Vulkan support
Contact:

Re: GZDoom 3.6.0 fatal crash ()

Post by Player701 »

Well, GZDoom does give an error message just before crashing, at least in the latest devbuild git version (g3.7pre-771-g4a83f4d25): "Invalid function identifier".

The problem is that the FxNop object that is created when this error message is produced doesn't have a ValueType set, and the code generator then tries to get an integer constant from it. The code in FxIntCast::Resolve is not prepared to handle situations when ValueType of the base expression is null, so it makes GZDoom crash. FxNop should probably have its ValueType set to something meaningful, shouldn't it?
Post Reply

Return to “Closed Bugs [GZDoom]”