Commit 85e767e
committed
Fix: segfault when reading tin of NON_PM monster
This is yet another bug due to the failure to realize NON_PM is -1, not
0. Apparently this segfault would only happen when there is a NON_PM tin
which is not spinach, which should not be possible as far as I know. Add
an impossible case to handle that rather than letting it segfault.1 parent 3e1fe5a commit 85e767e
1 file changed
Lines changed: 6 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
292 | 292 | | |
293 | 293 | | |
294 | 294 | | |
295 | | - | |
| 295 | + | |
296 | 296 | | |
297 | 297 | | |
298 | 298 | | |
299 | | - | |
| 299 | + | |
| 300 | + | |
300 | 301 | | |
301 | 302 | | |
| 303 | + | |
| 304 | + | |
| 305 | + | |
302 | 306 | | |
303 | 307 | | |
304 | 308 | | |
| |||
0 commit comments