Re: [Gnash-dev] std::bad_cast

[Andrea Palmatè]

I'm discovering a lot of interesting things..

First of all i was using a buggy g++
For the test i'm using a Debian with trunk version of gnash to see  
differences between aos4 and linux and i'm testing the same files.
I've seen that with linux almost all files are played correctly except  
a few ones
I've used a gcc 4.2.3 now instead 4.2.4 and a file that with other  
compiler doesn't play correctly now is ok
I discover this thing because i was sure i've played it in the past..

But i have a file that instead is not played correctly with linux and  
my current version of gnash while is played correctly with my old  
4.2.4 version of gnash..
that's crazy...

Another point.
i'm logging Shm:: functions to see if they are called and executed  
correctly and that file seems to use it
I'll attach it. Can you try it with your version of gnash?

Andrea

player195.swf
Description: Binary data

Il giorno 11/mag/09, alle ore 23:31, Benjamin Wolsey ha scritto:

> >         catch (...) // unexpected, unknown, but why not cleaning up...
>
> The answer to the question in the comment is that it hides bugs in
> implementation or in Gnash.
>
> > i would expected that a throw will be called but instead i don't
> > receive bad_cast anymore
>
> That's surely because it's caught in (...) and not logged any more,  
> but
> still you get no abort.
>
> You shouldn't use an ifdef here, as it applies to all platforms. Just
> drop the two catches for exceptions Gnash isn't supposed to throw and
> see where the bad_cast is thrown from. I imagine it's also possible to
> do this with gdb without changing the code.
>
> bwy
>
> --
> Free Flash, use Gnash
> http://www.gnu.org/software/gnash/
>
> Benjamin Wolsey, Software Developer - http://benjaminwolsey.de