DECORATE parser crashes instead of fails
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.
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.
- Major Cooke
- Posts: 8212
- Joined: Sun Jan 28, 2007 3:55 pm
- Preferred Pronouns: He/Him
- Operating System Version (Optional): Windows 10
- Graphics Processor: nVidia with Vulkan support
- Location: GZBoomer Town
- Contact:
DECORATE parser crashes instead of fails
If there's one thing I noticed, it's that when something wrong is picked up (such as Pick instead of RandomPick), the decorate parser tends to just crash which isn't very helpful when trying to find out where or when the problem occurred in the decorate code. It keeps generating an access violation instead of showing "Execution could not continue."
- Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 49247
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: DECORATE parser crashes instead of fails
Can you make an example definition to test it? I have never experienced such a thing.
- Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 49247
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: DECORATE parser crashes instead of fails
Again: No demonstration, no investigation, no fix. You really should now better than to abandon your bug reports and not provide feedback when requested.
I tried with a simple deliberate error and it output the message as expected.
I tried with a simple deliberate error and it output the message as expected.
- Major Cooke
- Posts: 8212
- Joined: Sun Jan 28, 2007 3:55 pm
- Preferred Pronouns: He/Him
- Operating System Version (Optional): Windows 10
- Graphics Processor: nVidia with Vulkan support
- Location: GZBoomer Town
- Contact:
Re: DECORATE parser crashes instead of fails
Yeah. I meant to reply to this thread, turns out it was a simple problem with blzut's build of GZdoom which we have fixed, from the drd team in this case.