Bug 151939

Summary:	Sequence diagram crashes when creating messages without parameter type
Product:	[Applications] umbrello	Reporter:	Carsten Høilund <carsten.hoilund>
Component:	general	Assignee:	Umbrello Development Group <umbrello-devel>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	cfeck, ralf.habacker
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	.xmi where the crash can easily be reproduced

Description Carsten Høilund 2007-11-06 14:04:36 UTC

Version:           1.5.8 (using KDE KDE 3.5.8)
Installed from:    00

When creating a message from ClassA to ClassB and the function in ClassB takes an argument whose type has not been defined causes Umbrello to crash. Defining the type of the argument prevents the crash.

Console output:
kbuildsycoca running...
umbrello: WARNING: returning 0 at UMLListView::findView
umbrello: WARNING: returning 0 at UMLListView::findView
umbrello: WARNING: returning 0 at UMLListView::findView
umbrello: WARNING: returning 0 at UMLListView::findView
KCrash: Application 'umbrello' crashing...
Could not find 'drkonqi' executable.
KCrash cannot reach kdeinit, launching directly.

The four warnings appear before trying to add any messages.

Comment 1 Carsten Høilund 2007-11-06 14:07:47 UTC

Created attachment 22006 [details]
.xmi where the crash can easily be reproduced

This attachment can be used to reproduce the bug. Just create a message from
ClassA to ClassB using "crash(param : )". Using "ok(param : int)" does not
cause a crash.

Comment 2 Christoph Feck 2011-12-20 02:58:31 UTC

This crash report is at least 4 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in KDE 4 or the backtrace is no longer applicable to KDE 4.

If the crash still happens with a recent KDE version (4.7.4 or 4.8), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or NEW)