diff options
| author | Simon Tatham <anakin@pobox.com> | 2015-10-21 18:32:15 +0100 |
|---|---|---|
| committer | Simon Tatham <anakin@pobox.com> | 2015-10-21 18:32:15 +0100 |
| commit | 1cf403ceb81482dea7107a49573d6834c5a650d1 (patch) | |
| tree | 04c954af41db6ac10931625bf098cf84bb22d75f /html/map.html | |
| parent | 90af15b43ed57a6835091bb1c98227052590b3ea (diff) | |
| download | puzzles-1cf403ceb81482dea7107a49573d6834c5a650d1.zip puzzles-1cf403ceb81482dea7107a49573d6834c5a650d1.tar.gz puzzles-1cf403ceb81482dea7107a49573d6834c5a650d1.tar.bz2 puzzles-1cf403ceb81482dea7107a49573d6834c5a650d1.tar.xz | |
Fix array overruns in the new Filling solver pass.
Probably because I wrote a couple of loops up to the maximum cell
value using the non-idiomatic <= for their termination test, I also
managed to use <= inappropriately for iterating over every cell of the
grid, leading to a couple of references just off the end of arrays.
Amusingly, it was the Emscripten front end which pointed this out to
me by actually crashing as a result! Though valgrind found it just
fine too, once I thought to run that. But it comes to something when
running your C program in Javascript detects your memory errors :-)
Diffstat (limited to 'html/map.html')
0 files changed, 0 insertions, 0 deletions