by Guest » Tue Jan 15, 2019 7:09 am
This is kinda weird. I've compiled the latest GZDoom commit as of this writing (703cb9cf), and there's two ways I've found to crash the game nearly instantly.
The first way is to add a console command to the command line (assertion fails). I can reliably cause GZDoom to crash within two seconds with the command `gzdoom -config /dev/null -iwad ~/.iwads/doom2.wad +echo "butt"`. Changing the command to "eval + 1 1" crashes too. Setting a CVar (eg. "sv_freelook 0") doesn't crash. Here's the backtrace (although it doesn't look that useful):
https://www.hastebin.com/rajiwodebi.txt
The other way I can get the game to crash is if I use the automap key on the title screen (access violation). The command is the same as the first, minus the echo line. Here's the backtrace:
https://www.hastebin.com/ebeciyobil.txt
I'm not sure if these occur on Windows, but I wouldn't be surprised if they do.
This is kinda weird. I've compiled the latest GZDoom commit as of this writing (703cb9cf), and there's two ways I've found to crash the game nearly instantly.
The first way is to add a console command to the command line (assertion fails). I can reliably cause GZDoom to crash within two seconds with the command `gzdoom -config /dev/null -iwad ~/.iwads/doom2.wad +echo "butt"`. Changing the command to "eval + 1 1" crashes too. Setting a CVar (eg. "sv_freelook 0") doesn't crash. Here's the backtrace (although it doesn't look that useful): https://www.hastebin.com/rajiwodebi.txt
The other way I can get the game to crash is if I use the automap key on the title screen (access violation). The command is the same as the first, minus the echo line. Here's the backtrace: https://www.hastebin.com/ebeciyobil.txt
I'm not sure if these occur on Windows, but I wouldn't be surprised if they do.