aboutsummaryrefslogtreecommitdiff
path: root/html/range.html
diff options
context:
space:
mode:
authorBen Harris <bjh21@bjh21.me.uk>2023-02-14 13:16:53 +0000
committerBen Harris <bjh21@bjh21.me.uk>2023-04-08 20:08:16 +0100
commit71cf891fdc3ab237ecf0e5d1aae39b6c9fe97a4d (patch)
tree815e735ad2358533808c5949e767d52b059a7f90 /html/range.html
parenta4c6f21b8e286322d3c1820785907a000fe1092f (diff)
downloadpuzzles-71cf891fdc3ab237ecf0e5d1aae39b6c9fe97a4d.zip
puzzles-71cf891fdc3ab237ecf0e5d1aae39b6c9fe97a4d.tar.gz
puzzles-71cf891fdc3ab237ecf0e5d1aae39b6c9fe97a4d.tar.bz2
puzzles-71cf891fdc3ab237ecf0e5d1aae39b6c9fe97a4d.tar.xz
Don't allow zero clues in Pattern
Some nonogram implementations allow zero clues so that a row or column with a single zero clue is equivalent to one with no clues, that is it has no black squares in it. Pattern, however, doesn't interpret them like this and treats a puzzle with a zero clue as insoluble, so it's not helpful to permit them. Permitting zero clues also confuses Pattern's memory allocation so that it can suffer a buffer overrun. As an example, before this commit a build with AddressSanitizer would report a buffer overrun with the description "1:0/0.0" because it tries to put two clues in a row that can have a maximum of one.
Diffstat (limited to 'html/range.html')
0 files changed, 0 insertions, 0 deletions