[Scummvm-git-logs] scummvm master -> 61eae101edc295e32254eee05b387c5ffb320dbc
athrxx
noreply at scummvm.org
Wed Aug 3 19:43:23 UTC 2022
This automated email contains information about 1 new commit which have been
pushed to the 'scummvm' repo located at https://github.com/scummvm/scummvm .
Summary:
61eae101ed SCUMM: properly initilize array (follow-up to 4248e22)
Commit: 61eae101edc295e32254eee05b387c5ffb320dbc
https://github.com/scummvm/scummvm/commit/61eae101edc295e32254eee05b387c5ffb320dbc
Author: athrxx (athrxx at scummvm.org)
Date: 2022-08-03T21:43:06+02:00
Commit Message:
SCUMM: properly initilize array (follow-up to 4248e22)
(the array is now 7 bytes larger than before, so it doesn't get reset completely in getWordVararg())
Changed paths:
engines/scumm/script_v5.cpp
diff --git a/engines/scumm/script_v5.cpp b/engines/scumm/script_v5.cpp
index 07e3c11416f..3843fff4437 100644
--- a/engines/scumm/script_v5.cpp
+++ b/engines/scumm/script_v5.cpp
@@ -784,6 +784,7 @@ void ScummEngine_v5::o5_chainScript() {
void ScummEngine_v5::o5_cursorCommand() {
int i, j, k;
int table[32];
+ memset(table, 0, sizeof(table));
switch ((_opcode = fetchScriptByte()) & 0x1F) {
case 1: // SO_CURSOR_ON
_cursor.state = 1;
More information about the Scummvm-git-logs
mailing list