FAangband 2.0.0
Collapse
X
-
I'm looking at every ocurrence of memset (I have the feeling that a large portion of the memory is wiped in some place). This line seems strange in ui-term.c (2626):
/* Assume no key */
memset(ch, 0, sizeof *ch);
It's valid ?Comment
-
I once had an issue with the Angband Android app because of a storage permission issue. I had to move the directory out of the Android/data folder to fix it. Could this be somehow related to the scoped storage system with Android 11?
Edit: that was with an old phone. Currently the game is installed to Android/data.Comment
-
I think it's just zeroing the memory that's going to store a keypress, so it looks fine to me. Also it's been there for 10 years without causing a problemOne for the Dark Lord on his dark throne
In the Land of Mordor where the Shadows lie.Comment
-
I had some problems with Android 10 concerning storage. I don't know if it's related to this.
There is a long standing bug in the android port that arises once in a while. A monster race pointer becomes null and the game crashes.
"...Google reports a lot of errors in mon_take_hit, get_lore, player_kill_monster. All related in some way to an invalid mon->race pointer..."
As I said, perhaps a rogue memset is wiping a chunk of memory.Comment
-
Comment
-
One for the Dark Lord on his dark throne
In the Land of Mordor where the Shadows lie.Comment
-
Code:env CFLAGS="-O2" ./configure --enable-release --enable-win --disable-curses --build=i686-pc-linux-gnu --host=i686-w64-mingw32
Comment
-
The latest builds should not have the crash on moving house, thanks to backwardsEric for finding and fixing the bug.
It seems that someone had put some essential code inside an assert(), and then optimised out asserts in release builds...One for the Dark Lord on his dark throne
In the Land of Mordor where the Shadows lie.Comment
Comment