[Top][All Lists]

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

[Gnash-commit] [bug #37077] segfault in[a85b5000+47000

From: Paul Menzel
Subject: [Gnash-commit] [bug #37077] segfault in[a85b5000+47000]
Date: Wed, 12 Dec 2012 09:58:01 +0000
User-agent: Mozilla/5.0 (X11; Linux) AppleWebKit/535.22 (KHTML, like Gecko) Chrome/18.0.1025.133 Safari/535.22 Midori/0.4

Follow-up Comment #8, bug #37077 (project gnash):

Ok, looking at the backtrace again,

        #0  0xa79488d3 in gnash::GnashPluginScriptObject::readPlayer
(address@hidden, fd=6881392)
            at ../../../plugin/npapi/pluginScriptObject.cpp:717
        #1  0xa7948b2f in gnash::GnashPluginScriptObject::readPlayer
(this=0xa67e2168) at ../../../plugin/npapi/pluginScriptObject.cpp:698
        #2  0xb317d5f4 in ?? () from /usr/lib/i386-linux-gnu/
        Backtrace stopped: previous frame inner to this frame (corrupt

the method(?)/function(?) is called by Gnash’s own

            return readPlayer(_hostfd);

This uses the variable `_hostfd` which is a class variable(?) and managed by

The constructor reads

        // Constructor
            : _nppinstance (0),
        //    log_debug(__PRETTY_FUNCTION__);

so `_hostfd` is set to `-1` by default. `hostfd_` is not manipulated afterward
in that class. But it has to be, as it is set to some high value when the
segmentation fault happens.

Could you shed some more light on this, please? From the analysis above, I
think now it is indeed a Gnash problem.


Reply to this item at:


  Nachricht gesendet von/durch Savannah

reply via email to

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