On Thu, Dec 22, 2011 at 09:16:16AM +0530, niraj kulkarni wrote:
> Attached the swf file.
Please don't. Use the tracker if possible, or some other web space.
4.5Mb for a single email isn't fun.
> 1. Regarding decompilation, I tried to match code sequences in disassembly
> generated by listswf and actual code path used by -va argument. But since
> it was huge data, it is impossible to find out a fault (at least as a
> beginner). Additionally listswf generated a file with some non ascii
> symbols, thus making a bit difficult to correlate with other file. So any
> suggestion for this debug path?
Try flasm to inject debuggin traces into the code.
> 2. Is there any main render call, which will act like a gate to other
> render engines, ie all display call will go through that call before being
> redirected to respective render engine? I think it would be a bit easy to
> backtrack from that call to find out what is happening in swf.
movie_root::advance is the main action execution code.
This bug is most likely related to AS more than rendering.