Version: 1.3.0_devel (using KDE 3.4.0, compiled sources) Compiler: gcc version 3.4.3 OS: SunOS (sun4u) release 5.8 Well, the title says it all: it seems that the 32nd curve being created in one go with the datawizard crashes kst when hitting "Finish". The following is spat out shortly before death: "QGArray::at: Absolute index 0 out of range" More details follow: Program received signal SIGSEGV, Segmentation fault. 0x0086969f in KstViewObject::cleanup () from /ldk/0/soft/kde3.5/lib/libkstapp.so.1 (gdb) where #0 0x0086969f in KstViewObject::cleanup () from /ldk/0/soft/kde3.5/lib/libkstapp.so.1 #1 0x0080aa29 in KstTopLevelView::createObject<Kst2DPlot> () from /ldk/0/soft/kde3.5/lib/libkstapp.so.1 #2 0x0080b901 in KstViewWindow::createObject<Kst2DPlot> () from /ldk/0/soft/kde3.5/lib/libkstapp.so.1 #3 0x0097f6dd in DataWizard::finished () from /ldk/0/soft/kde3.5/lib/libkstapp.so.1 #4 0x0098e6f7 in DataWizard::qt_invoke () from /ldk/0/soft/kde3.5/lib/libkstapp.so.1 #5 0x02d15a7c in QObject::activate_signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #6 0x02d158a4 in QObject::activate_signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #7 0x03058b7e in QButton::clicked () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #8 0x02da796a in QButton::mouseReleaseEvent () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #9 0x02d4ba17 in QWidget::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #10 0x02cb99ff in QApplication::internalNotify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #11 0x02cb90f4 in QApplication::notify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #12 0x027582bc in KApplication::notify () from /ldk/0/soft/kde3.5/lib/libkdecore.so.4 #13 0x02c50220 in QETWidget::translateMouseEvent () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #14 0x02c4deac in QApplication::x11ProcessEvent () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #15 0x02c64c34 in QEventLoop::processEvents () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #16 0x02ccbbf8 in QEventLoop::enterLoop () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #17 0x02cb9cb1 in QApplication::enter_loop () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #18 0x02e9e3e0 in QDialog::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #19 0x0093004e in KstApp::showDataWizardWithFile () from /ldk/0/soft/kde3.5/lib/libkstapp.so.1 #20 0x08053a42 in main ()
Wow, I even knew this would happen! The number of columns was artificially limited to 32-1. I just bumped it to 10-1=9 bits.
SVN commit 532181 by staikos: I knew it wasn't enough :-) BUG: 125817 M +1 -1 kstviewobject.h --- trunk/extragear/graphics/kst/src/libkstapp/kstviewobject.h #532180:532181 @@ -313,7 +313,7 @@ bool _container : 1; bool _fallThroughTransparency : 1; bool _isResizable : 1; - int _columns : 6; // "64 columns ought to be enough for anyone" + int _columns : 10; QGuardedPtr<KstViewObject> _topObjectForMenu; QGuardedPtr<KstViewObject> _parent; // danger!! Q_UINT32 _standardActions, _layoutActions;
Nice that you fixed it, but loading > 31 vectors does not necessarily mean we want more than 31 columns ! Well, I suppose it is first loaded that way and the actual layout is reorganized before it is drawn...