Bug 271363 - Undoing synchronous messages in sequence diagram
Summary: Undoing synchronous messages in sequence diagram
Status: RESOLVED FIXED
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: 2.4.5
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Umbrello Development Group
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-20 17:57 UTC by olli.myohanen
Modified: 2014-01-04 11:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 4.13.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description olli.myohanen 2011-04-20 17:57:13 UTC
Application: umbrello (2.4.5)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-30-generic x86_64
Distribution: Ubuntu 10.04.2 LTS

-- Information about the crash:
I tried to create a sequence diagram with several "overlapping" synchronous messages. Umbrello was not exactly doing what I was hoping for and it ended up in bit of a mess. I tried to press Undo several times to get rid of the changes and that's when the program crashed. 

 -- Backtrace:
Application: Umbrello UML Modeller (umbrello), signal: Segmentation fault
[KCrash Handler]
#5  0x0000000000ad5e20 in ?? ()
#6  0x00007f5eef699e01 in QUndoStack::undo() () from /usr/lib/libQtGui.so.4
#7  0x00007f5eef6bd390 in QUndoStack::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtGui.so.4
#8  0x00007f5eeeb58e3f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#9  0x00007f5eef013032 in QAction::triggered(bool) () from /usr/lib/libQtGui.so.4
#10 0x00007f5eef0150ab in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQtGui.so.4
#11 0x00007f5eef0169b7 in QAction::event(QEvent*) () from /usr/lib/libQtGui.so.4
#12 0x00007f5eef01922c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#13 0x00007f5eef01f6fb in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#14 0x00007f5ef0420a16 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#15 0x00007f5eeeb4606c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#16 0x00007f5eef054e86 in ?? () from /usr/lib/libQtGui.so.4
#17 0x00007f5eef056c97 in ?? () from /usr/lib/libQtGui.so.4
#18 0x00007f5eef021268 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#19 0x00007f5ef0420a16 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#20 0x00007f5eeeb4606c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#21 0x00007f5eef0c416a in ?? () from /usr/lib/libQtGui.so.4
#22 0x00007f5eef0c66f0 in ?? () from /usr/lib/libQtGui.so.4
#23 0x00007f5eef09d904 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4
#24 0x00007f5eef0c9882 in ?? () from /usr/lib/libQtGui.so.4
#25 0x00007f5eea3968c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#26 0x00007f5eea39a748 in ?? () from /lib/libglib-2.0.so.0
#27 0x00007f5eea39a8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#28 0x00007f5eeeb6f513 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#29 0x00007f5eef0c946e in ?? () from /usr/lib/libQtGui.so.4
#30 0x00007f5eeeb44992 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#31 0x00007f5eeeb44d6c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#32 0x00007f5eeeb48aab in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#33 0x0000000000b6c6c5 in ?? ()
#34 0x00007f5eed7a7c4d in __libc_start_main () from /lib/libc.so.6
#35 0x0000000000435839 in _start ()

This bug may be a duplicate of or related to bug 266789.

Possible duplicates by query: bug 270535, bug 267002, bug 266789, bug 264214, bug 262848.

Reported using DrKonqi