gnash-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-dev] debugging bug #34975 Rollercoaster rush game


From: Sandro Santilli
Subject: Re: [Gnash-dev] debugging bug #34975 Rollercoaster rush game
Date: Sat, 17 Dec 2011 21:41:48 +0100
User-agent: Mutt/1.5.20 (2009-06-14)

On Sat, Dec 17, 2011 at 07:11:58PM +0530, niraj kulkarni wrote:
> Hi,
>     I am a new-bie developer here. I am trying to debug this problem.
> Please suggest me possible solutions.
> 
> Basically I've used gdb + verbose gnash to find out that it tries to load 2
> other files other than original game swf file.
> It succeeds to fetch first file, which is again a swf file, but gives error
> while fetching other file. I've tried to manually fetch he error prone file,
> and found that no such file on given link exists. (even CURL gives same
> error for gnash)c.
> 
> I've found out that for running the game these other files are not
> necessary. I've tried running game swf offline on other flash player and it
> plays.

Excellent progress so far. I suggest you then attach the file to the ticket.
I'm assuming Gnash is still failing with the offline version ?

> So can anybody suggest possible causes of problem and suggestion for
> solution?

Could it have to do with load events ? like onError or such ?
You may try to disassemble the SWF to see what it does, Ming's
listswf_d is an excellent tool for that.

> Another thing is the bug report indicates a line from log "32495:1] 8591
> ERROR: No fn_call::callerDef in string function call" whereas I havent seen
> such line in verbose output,
> so what do I need to do to get these log dumps?

It sounds like a call generated by an event, you may turn that log_error
into an assertion failure and check with gdb what's the originating code.

--strk; 

  ,------o-. 
  |   __/  |    Thank you for PostGIS-2.0 Topology !
  |  / 2.0 |    http://www.pledgebank.com/postgistopology
  `-o------'




reply via email to

[Prev in Thread] Current Thread [Next in Thread]