fix issue #337 - crash on start with armhf arch
Fix "objects[0] class #1 not in order!" panic. The new check to make sure that the elements of objects[] were in ascending order by object class uses a plain 'char' index so -1 to indicate 'no previous value' didn't work on a system using unsigned chars. Verfied by temporarily adding '-funsigned-char' to CFLAGS before and after the revision. Before: panic, after: no panic. Fixes #337
This commit is contained in:
@@ -210,6 +210,7 @@ poison gas clouds located over known but unlit pools were visible as known
|
||||
after the wish parsing change, wishing for "<something of monster>" or for
|
||||
"<monster something>" worked as intended but wishing for "<monster>"
|
||||
(where <monster> used the canonical spelling) triggered a crash
|
||||
fix new "objects[0] class #1 not in order!" panic if plain 'char' is unsigned
|
||||
tty: redraw unexplored locations as S_unexplored rather than <space> after
|
||||
map has been partially overwritten by popup menu or text display
|
||||
tty: previous change resulted in remnants of previous level being shown on
|
||||
|
||||
Reference in New Issue
Block a user