Dungeongen: Fix rarely triggered segfault

A segfault exposed a missing 'vm->m_area.contains()'
check in makeCorridor that allowed the calculation
of vm index for a node outside the vm area. The huge
and invalid index number caused getContent to fail
This commit is contained in:
paramat 2015-11-30 01:43:28 +00:00
parent 6fead2818a
commit 57b429574e

@ -392,7 +392,8 @@ void DungeonGen::makeCorridor(v3s16 doorplace, v3s16 doordir,
if (partcount != 0) if (partcount != 0)
p.Y += make_stairs; p.Y += make_stairs;
if (vm->m_area.contains(p) && vm->m_area.contains(p + v3s16(0, 1, 0))) { if (vm->m_area.contains(p) && vm->m_area.contains(p + v3s16(0, 1, 0)) &&
vm->m_area.contains(v3s16(p.X - dir.X, p.Y - 1, p.Z - dir.Z))) {
if (make_stairs) { if (make_stairs) {
makeFill(p + v3s16(-1, -1, -1), makeFill(p + v3s16(-1, -1, -1),
dp.holesize + v3s16(2, 3, 2), dp.holesize + v3s16(2, 3, 2),