Bug 272276 - Crash when drawing a new synchronous message.
Summary: Crash when drawing a new synchronous message.
Status: RESOLVED DUPLICATE of bug 168752
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Umbrello Development Group
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-02 21:34 UTC by damien.rieu
Modified: 2012-07-05 23:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description damien.rieu 2011-05-02 21:34:09 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-31-generic-pae i686
Distribution: Ubuntu 10.04.2 LTS

-- Information about the crash:
I try to draw an assynchronous message and umbrello crash.

 -- Backtrace:
Application: Umbrello - Outil de modélisation UML (umbrello), signal: Segmentation fault
[Current thread is 1 (Thread 0xb501c710 (LWP 3904))]

Thread 2 (Thread 0xb2541b70 (LWP 3905)):
#0  0xb76f4430 in __kernel_vsyscall ()
#1  0xb590ab86 in *__GI___poll (fds=0xb59a0ff4, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#2  0xb52ce4eb in g_poll () from /lib/libglib-2.0.so.0
#3  0xb52c10ac in ?? () from /lib/libglib-2.0.so.0
#4  0xb52c14b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0xb5f8360f in QEventDispatcherGlib::processEvents (this=0x9813900, flags=...) at kernel/qeventdispatcher_glib.cpp:414
#6  0xb5f56059 in QEventLoop::processEvents (this=0xb2541290, flags=) at kernel/qeventloop.cpp:149
#7  0xb5f564aa in QEventLoop::exec (this=0xb2541290, flags=...) at kernel/qeventloop.cpp:201
#8  0xb5e525a8 in QThread::exec (this=0x9811f48) at thread/qthread.cpp:487
#9  0xb5f35c1b in QInotifyFileSystemWatcherEngine::run (this=0x9811f48) at io/qfilesystemwatcher_inotify.cpp:248
#10 0xb5e5532e in QThreadPrivate::start (arg=0x9811f48) at thread/qthread_unix.cpp:248
#11 0xb5dc896e in start_thread (arg=0xb2541b70) at pthread_create.c:300
#12 0xb5918a4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb501c710 (LWP 3904)):
[KCrash Handler]
#6  QString (this=0x0) at /usr/include/qt4/QtCore/qstring.h:714
#7  UMLObject::getName (this=0x0) at ../../../umbrello/umbrello/umlobject.cpp:186
#8  0x0867410c in UMLClassifier::findOperation (this=0x9be7738, name=..., params=) at ../../../umbrello/umbrello/classifier.cpp:193
#9  0x0863dd7b in FloatingTextWidget::showOperationDialog (this=0x9f70b80) at ../../../umbrello/umbrello/widgets/floatingtextwidget.cpp:358
#10 0x086c9e0c in ToolBarStateMessages::setSecondWidget (this=0x9e26410, secondObject=0x9bd5cf0, messageType=ToolBarStateMessages::NormalMessage)
    at ../../../umbrello/umbrello/toolbarstatemessages.cpp:293
#11 0x086c9f86 in ToolBarStateMessages::mouseReleaseWidget (this=0x9e26410) at ../../../umbrello/umbrello/toolbarstatemessages.cpp:165
#12 0x086c7236 in ToolBarState::mouseRelease (this=0x9e26410, ome=0xbff555f0) at ../../../umbrello/umbrello/toolbarstate.cpp:123
#13 0xb5c2b188 in Q3ScrollView::viewportMouseReleaseEvent (this=0x9a92fb8, e=0xbff55b70) at widgets/q3scrollview.cpp:1763
#14 0xb5c2cf78 in Q3ScrollView::eventFilter (this=0x9a92fb8, obj=0x9ab5050, e=0xbff55b70) at widgets/q3scrollview.cpp:1481
#15 0xb5f56cda in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x95c6170, receiver=0x9ab5050, event=0xbff55b70) at kernel/qcoreapplication.cpp:819
#16 0xb61a24b9 in QApplicationPrivate::notify_helper (this=0x95c6170, receiver=0x9ab5050, e=0xbff55b70) at kernel/qapplication.cpp:4296
#17 0xb61a99f7 in QApplication::notify (this=0xbff56420, receiver=0x9ab5050, e=0xbff55b70) at kernel/qapplication.cpp:3865
#18 0xb6f7e40a in KApplication::notify (this=0xbff56420, receiver=0x9ab5050, event=0xbff55b70) at ../../kdeui/kernel/kapplication.cpp:302
#19 0xb5f57a3b in QCoreApplication::notifyInternal (this=0xbff56420, receiver=0x9ab5050, event=0xbff55b70) at kernel/qcoreapplication.cpp:704
#20 0xb61a8952 in QCoreApplication::sendEvent (receiver=0x9ab5050, event=0xbff55b70, alienWidget=0x9ab5050, nativeWidget=0x9a92fb8, buttonDown=0xb6ae6058, lastMouseReceiver=..., spontaneous=true)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#21 QApplicationPrivate::sendMouseEvent (receiver=0x9ab5050, event=0xbff55b70, alienWidget=0x9ab5050, nativeWidget=0x9a92fb8, buttonDown=0xb6ae6058, lastMouseReceiver=..., spontaneous=true)
    at kernel/qapplication.cpp:2965
#22 0xb6234088 in QETWidget::translateMouseEvent (this=0x9a92fb8, event=0xbff5608c) at kernel/qapplication_x11.cpp:4368
#23 0xb6233511 in QApplication::x11ProcessEvent (this=0xbff56420, event=0xbff5608c) at kernel/qapplication_x11.cpp:3379
#24 0xb626260a in x11EventSourceDispatch (s=0x95c93a8, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#25 0xb52bd5e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#26 0xb52c12d8 in ?? () from /lib/libglib-2.0.so.0
#27 0xb52c14b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#28 0xb5f835d5 in QEventDispatcherGlib::processEvents (this=0x95a8c20, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#29 0xb6262135 in QGuiEventDispatcherGlib::processEvents (this=0x95a8c20, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#30 0xb5f56059 in QEventLoop::processEvents (this=0xbff56384, flags=) at kernel/qeventloop.cpp:149
#31 0xb5f564aa in QEventLoop::exec (this=0xbff56384, flags=...) at kernel/qeventloop.cpp:201
#32 0xb5f5a69f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#33 0xb61a2577 in QApplication::exec () at kernel/qapplication.cpp:3579
#34 0x086ac645 in main (argc=3, argv=0xbff565d4) at ../../../umbrello/umbrello/main.cpp:111

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

Possible duplicates by query: bug 168752.

Reported using DrKonqi
Comment 1 damien.rieu 2011-05-02 21:40:58 UTC
I reproduce the bug every time I've made the same asynchronous message :
Class X to Class Y.
With other class there is no problem.I can make the asynchronous message.
Comment 2 Jekyll Wu 2012-07-05 23:46:19 UTC

*** This bug has been marked as a duplicate of bug 168752 ***