Version: current cvs (using KDE Devel) Installed from: Compiled sources Compiler: gcc 3.3.1 OS: Linux When I create an association, aka operation between two object in a collab. diag., then delete it, Umbrello crashes. This has something to do with the fact that when I want to create the operation, it is created as some m299998 or something similar name. Umbrello says on stdout/stderr : umbrello: UMLView::addWidget (AAttachment type=312): position (0,0) is out of range The crash report is: [New Thread 16384 (LWP 2101)] [KCrash handler] #5 0x0819a9cc in UMLView::saveToXMI(QDomDocument&, QDomElement&) () #6 0x08175cc5 in UMLDoc::saveToXMI(QIODevice&) () #7 0x0817be76 in UMLDoc::addToUndoStack() () #8 0x0817ab02 in UMLDoc::setModified(bool, bool) () #9 0x08192678 in UMLView::removeWidget(UMLWidget*) () #10 0x081038ef in AssociationWidget::cleanup() () #11 0x08101488 in AssociationWidget::~AssociationWidget() () #12 0x0810c7de in QPtrList<AssociationWidget>::deleteItem(void*) () #13 0x41014880 in QGList::remove(void*) () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #14 0x0819dea3 in QPtrList<AssociationWidget>::remove(AssociationWidget const*) () #15 0x081972c6 in UMLView::removeAssoc(AssociationWidget*) () #16 0x081978fa in UMLView::removeAssociations(UMLWidget*) () #17 0x081925d0 in UMLView::removeWidget(UMLWidget*) () #18 0x08192f2f in UMLView::deleteSelection() () #19 0x0816b2a5 in UMLApp::slotDeleteSelectedWidget() () #20 0x0816be8e in UMLApp::qt_invoke(int, QUObject*) () #21 0x40d0f84f in QObject::activate_signal(QConnectionList*, QUObject*) () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #22 0x40d0f61a in QObject::activate_signal(int) () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #23 0x405a9e25 in KAction::activated() () from /opt/kdeqt3.2/lib/libkdeui.so.4 #24 0x405a952c in KAction::slotActivated() () from /opt/kdeqt3.2/lib/libkdeui.so.4 #25 0x405a9ecc in KAction::qt_invoke(int, QUObject*) () from /opt/kdeqt3.2/lib/libkdeui.so.4 #26 0x40d0f84f in QObject::activate_signal(QConnectionList*, QUObject*) () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #27 0x40d0f61a in QObject::activate_signal(int) () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #28 0x408a7235 in KAccelPrivate::menuItemActivated() () from /opt/kdeqt3.2/lib/libkdecore.so.4 #29 0x408a3fd8 in KAccelPrivate::eventFilter(QObject*, QEvent*) () from /opt/kdeqt3.2/lib/libkdecore.so.4 #30 0x40d0d167 in QObject::activate_filters(QEvent*) () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #31 0x40d0d06d in QObject::event(QEvent*) () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #32 0x40d4a2d5 in QWidget::event(QEvent*) () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #33 0x40e1377a in QMainWindow::event(QEvent*) () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #34 0x40caa014 in QApplication::internalNotify(QObject*, QEvent*) () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #35 0x40ca9893 in QApplication::notify(QObject*, QEvent*) () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #36 0x40813097 in KApplication::notify(QObject*, QEvent*) () from /opt/kdeqt3.2/lib/libkdecore.so.4 #37 0x408a16d5 in KAccelEventHandler::x11Event(_XEvent*) () from /opt/kdeqt3.2/lib/libkdecore.so.4 #38 0x408191b2 in KApplication::x11EventFilter(_XEvent*) () from /opt/kdeqt3.2/lib/libkdecore.so.4 #39 0x40c2a4b3 in qt_x11EventFilter(_XEvent*) () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #40 0x40c34329 in QApplication::x11ProcessEvent(_XEvent*) () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #41 0x40c4c87b in QEventLoop::processEvents(unsigned) () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #42 0x40cbdbda in QEventLoop::enterLoop() () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #43 0x40cbdae4 in QEventLoop::exec() () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #44 0x40caa2c0 in QApplication::exec() () from /home/bartkozoltan/qt-3.2.3/lib/libqt-mt.so.3 #45 0x0814d086 in main ()
Hi Zoltan, I believe I've fixed it, could you please verify? Thanks.
The crash problem is fixed, which is great. However a message still has a default operation of m29998 for some reason and when you select messages with the mouse they are not highlighted at the ends.
> However a message still has a default operation of m29998 This is purposefully so. AFAIK the at_Coll_Message code depends on the collaboration message having a name. > [...] and when you select messages with the mouse they are > not highlighted at the ends. Puzzling. I've spent some time investigating this - without result. The strange thing is that the same works for other (i.e. non collaboration message) associations.
Closing this report as the crash is resolved. > [...] and when you select messages with the mouse they are > not highlighted at the ends. Feel free to open a new PR for that problem.