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

[Paul Menzel]

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/libstdc++.so.6
        Backtrace stopped: previous frame inner to this frame (corrupt
stack?)

the method(?)/function(?) is called by Gnash’s own
`gnash::GnashPluginScriptObject::readPlayer`.

        std::string
        GnashPluginScriptObject::readPlayer()
        {
            return readPlayer(_hostfd);
        }

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

The constructor reads

        // Constructor
        GnashPluginScriptObject::GnashPluginScriptObject()
            : _nppinstance (0),
              _controlfd(-1),
              _hostfd(-1)
        {
        //    log_debug(__PRETTY_FUNCTION__);
            
            initializeIdentifiers();
            
        }

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:

  <http://savannah.gnu.org/bugs/?37077>

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/