[Octave-bug-tracker] [bug #48519] Segfault with Qt plotting when running demos

[Lachlan Andrew]

Follow-up Comment #1, bug #48519 (project octave):

I've tried to reproduce this, and don't seem to be able to.

Thanks for providing a stack trace.  That really helps.  You can see that
slotUpdate is being called on a NULL object.  That means the bug must be in
QtHandles::ObjectProxy::update or earlier.  It seems that ObjectProxy::init is
not being called to set  m_object.

Can you see if the attached changeset makes a difference?


There are several Qt bugs that are system dependent. One thing you could do to
debug it is to look for the other problems with Qt and see if your system
reproduces any of them.

(My guess is that this is different, because those crashes were often in the
OpenGL drivers and this in in Octave code, but it is something to try.)

(file #37907)
    _______________________________________________________

Additional Item Attachment:

File name: bug_48519_qt_invalid_proxy.cset Size:0 KB


    _______________________________________________________

Reply to this item at:

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

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