[Scummvm-devel] Broken Sword 2 problem

[yotam barnoy]

To those who understand this engine (not me :) this is what's in
*(_curObjectHub.addr) right before the crash. Those don't seem like
proper values to me, but what do I know?

(Reminder -- it's little endian)

Yotam

8cb3b6c - 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00
08cb3b7c - 00 00 00 00 09 00 08 00 00 00 00 00 00 00 00 00
08cb3b8c - 39 00 00 00 00 00 00 00 00 00 00 00 40 05 00 00
08cb3b9c - 08 00 01 00 FD 02 00 00 00 00 00 00 00 00 00 00
08cb3bac - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
08cb3bbc - 00 00 00 00 00 00 00 00 00 00 00 00 18 01 00 00
08cb3bcc - 74 BF FF FF EE 02 00 00 4A 01 00 00 06 00 00 00
08cb3bdc - 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00
08cb3bec - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
08cb3bfc - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
08cb3c0c - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
08cb3c1c - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
08cb3c2c - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
08cb3c3c - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
08cb3c4c - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
08cb3c5c - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

On Thu, Aug 26, 2010 at 11:27 AM, yotam barnoy <yotambarnoy at gmail.com> wrote:
> I'm experiencing a very strange bug in BS2 on the PSP. I get an
> exception when starting from the beginning, and then skipping the
> movies. If I restore, it works fine.
>
> I tried to trace the problem, but it's very difficult. What I got to
> is that in logic.cpp line 135, script/SIZE is 0. This causes the
> system to go nuts.
> However, I can't trace the source of the problem since putting a
> printf on 'script' right before there causes the problem to go away!
> This is very bad as it means that the problem is one of a memory write
> into an improper place or a timing issue, both of which are very
> difficult to track.
>
> Can someone please run valgrind on Broken Sword 2 and see if they find
> anything? I'm trying to debug using assembly dumps but it seems the
> problem is too complex to corner that way.
>
> I thought the problem was related to my recent switch to the new read
> streams, but I can't find anything that would cause it, and it's quite
> possible that the new streams simply created the 'perfect storm'.
>
> Thanks
> Yotam
>