[Master] VM Abort when shooting a barrel in Harmony

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
Rachael
Posts: 13557
Joined: Tue Jan 13, 2004 1:31 pm
Preferred Pronouns: She/Her
Contact:

[Master] VM Abort when shooting a barrel in Harmony

Post by Rachael »



Harmony is available here

When shooting any of the "ExplosiveBarrel" types in Harmony, a VM abort is immediately caused. This happens even with +vm_jit 0.
_mental_
 
 
Posts: 3812
Joined: Sun Aug 07, 2011 4:32 am

Re: [Master] VM Abort when shooting a barrel in Harmony

Post by _mental_ »

The issue was introduced in this commit. It affects 3.7 release too.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
Posts: 49067
Joined: Sat Jul 19, 2003 10:19 am
Location: Germany

Re: [Master] VM Abort when shooting a barrel in Harmony

Post by Graf Zahl »

While the check is correct, it needs to be disabled if a state gets modified by Dehacked.
_mental_
 
 
Posts: 3812
Joined: Sun Aug 07, 2011 4:32 am

Re: [Master] VM Abort when shooting a barrel in Harmony

Post by _mental_ »

Is it about disabling of this check if the state was modified by Dehacked? Or is it about a whole FState::CheckCallerType() function?
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
Posts: 49067
Joined: Sat Jul 19, 2003 10:19 am
Location: Germany

Re: [Master] VM Abort when shooting a barrel in Harmony

Post by Graf Zahl »

The other checks would be crash issues, but that particular one needs to be disable for Dehacked-modified states, because the non-Actor functions that can be set here would otherwise cause an abort. All Dehacked-usable functions should contain enough safety checks to not crash.
_mental_
 
 
Posts: 3812
Joined: Sun Aug 07, 2011 4:32 am

Re: [Master] VM Abort when shooting a barrel in Harmony

Post by _mental_ »

Fixed in e353201.
Post Reply

Return to “Closed Bugs [GZDoom]”