Opened 16 years ago

Closed 16 years ago

#3549 closed defect (fixed)

lure crashes when waiting for patrol

Reported by: SF/tneumann Owned by: dreammaster
Priority: blocker Component: Engine: Lure
Version: Keywords:
Cc: Game: Lure of the Temptress


At one point during the gameplay (savegame attached) one has to wait in front of the shop for a patrol to enter the shop. This causes scummvm to crash, probably in the moment when the patrol should enter the screen.

To reproduce it load the attached save game and wait a bit (usually less than a minute). This is with scummvm-20071230.tar.bz2.

I tried to run scummvm in gdb but found no obvious bug. The stack trace is included below, apparently one of the NPCs has a NULL-pointer as hotspot, which causes a crash in npcWalkingCheck.

#0 0x000000000072ed26 in Lure::Hotspot::npcWalkingCheck (this=0x117bf00, hotspot=0x0) at engines/lure/hotspots.cpp:1988 #1 0x000000000072b698 in Lure::Hotspot::doAction (this=0x117bf00, action=Lure::NPC_WALKING_CHECK, hotspot=0x0) at engines/lure/hotspots.cpp:1271 #2 0x000000000072ba01 in Lure::Hotspot::npcSupportOffsetConditional ( this=0x117bf00, hotspot=0x0) at engines/lure/hotspots.cpp:2020 #3 0x000000000072b698 in Lure::Hotspot::doAction (this=0x117bf00, action=Lure::NPC_SUPPORT_OFFSET_COND, hotspot=0x0) at engines/lure/hotspots.cpp:1271 #4 0x000000000072b7df in Lure::Hotspot::doAction (this=0x117bf00) at engines/lure/hotspots.cpp:1207 #5 0x00000000007321af in Lure::HotspotTickHandlers::standardCharacterAnimHandler (h=@0x117bf00) at engines/lure/hotspots.cpp:2535 #6 0x000000000072793d in Lure::Hotspot::tick (this=0x117bf00) at engines/lure/hotspots.cpp:475

Ticket imported from: #1865552. Ticket imported from: bugs/3549.

Attachments (1)

lure.002 (19.7 KB ) - added by SF/tneumann 16 years ago.

Download all attachments as: .zip

Change History (6)

by SF/tneumann, 16 years ago

Attachment: lure.002 added

comment:1 by dreammaster, 16 years ago

Owner: set to dreammaster

comment:2 by dreammaster, 16 years ago

Priority: normalblocker

comment:3 by dreammaster, 16 years ago

Raising priority. This is a release-critical bug.

comment:4 by dreammaster, 16 years ago

Resolution: fixed
Status: newclosed

comment:5 by dreammaster, 16 years ago

This has been fixed - an incorrect value was being passed to get a hotspot pointer in the npcSupportOffsetConditional method, resulting in a null pointer error

Note: See TracTickets for help on using tickets.