address issue #1490 - rolling boulder segfault

Issue reported by BartekCupial:  segfault occurred and was tracked to
behavior of a rolling boulder trap.  Suggested fix was included, but it
assumes that the destination spot is valid so is suspect.

A comment pointed out that the path is validated when a rolling boulder
trap is created so the segfault should be impossible.  I didn't find an
explanation but am adding a fix based on the one in the issue report.

Closes #1490
This commit is contained in:
PatR
2026-04-25 13:14:33 -07:00
parent 89c7435b7a
commit 27f6ae340b
2 changed files with 18 additions and 0 deletions
+1
View File
@@ -1602,6 +1602,7 @@ when starting a new game as a monk, newsym(0,0) was being called (adjabil ->
postadjabil -> see_monsters when initializing See_invisible as hero
became level 1; seen 'monster' was the hero who hadn't been placed
on the map yet)
incorporate a fix to prevent segfault due to rolling boulder trap
Fixes to 3.7.0-x General Problems Exposed Via git Repository