[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    KDockWidget problem
From:       Carsten Pfeiffer <carpdjih () cetus ! zrz ! tu-berlin ! de>
Date:       2001-08-22 16:39:49
[Download RAW message or body]

Hi,

I just found out that quanta crashes with the following backtrace:

#4  0x8074277 in QuantaApp::slotDockChanged ()
#5  0x40b7ba5d in QObject::activate_signal () from /usr/lib/libqt.so.2
#6  0x4078f304 in KDockManager::change () from /opt/kde2/lib/libkdeui.so.3
#7  0x407842e8 in KDockWidget::undock () from /opt/kde2/lib/libkdeui.so.3
#8  0x40782b03 in KDockWidget::~KDockWidget () from /opt/kde2/lib/libkdeui.so.3
#9  0x40784cf3 in KDockManager::~KDockManager ()
   from /opt/kde2/lib/libkdeui.so.3
#10 0x40781680 in KDockMainWindow::~KDockMainWindow ()
   from /opt/kde2/lib/libkdeui.so.3
#11 0x8075a6f in QuantaApp::~QuantaApp ()

Is that on purpose that change() is emitted during destruction?

Looks like KDockWidget::undock() shouldn't emit manager->change() during destruction.
In fact, I wouldn't think that the huge undock() method should be called at all 
when the manager destroys all its children, but then, I've never messed with 
dock-widgets before.

Cheers
Carsten Pfeiffer

[prev in list] [next in list] [prev in thread] [next in thread]