Hi,
> The real real *real* problem seems to be that somewhere before
> gfxwop_dyn_view_draw(), the cel passed goes wrong. The cel
> parameter passed into this function contain different values after
> a certain point, as indicated by the asteriks below:
>
> This makes no sense to me, I would assume that memory corruption is
> happening somewheres? Here is some output from a print statement that
> prints the loop and cel parameters at the copy protection scene in LSL2.
The copy protection scene in LSL2 contains several semi-random cels and is
inappropriate for testing this.
Anyway, even if the cel was invalid, the gfx subsystem should fail
gracefully. It shouldn't write over the border of the visual area either,
since we're supposed to do clipping in the operational layer.
llap,
Christoph
