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

[Bastiaan Jacques]

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

> 1. What version of Midori do you run? I am using a self-build from latest
Git.

midori-0.4.6-1.fc17.x86_64

> 2. Did you open like 20 tabs from Phoronix. That triggers this usually in my
case.

Yes, lots of Flash activity seems to make it more likely to happen.

> 4. Any idea what I can do to provide more information to analyze the stack
corruption.

Not really. When faced with memory corruption problems I normally use Valgrind
to find where the problem starts, but running Midori in Valgrind leads to an
early segfault on my system before we get to any Flash content.

> 5. Should not the library/plugin return an error instead of segfaulting?

Absolutely. It is possible though that the segfault is ultimately caused by
Midori due to a bug in their NPAPI implementation, though.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/