Bug 102854 - C++ code import error
Summary: C++ code import error
Status: RESOLVED WORKSFORME
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: 1.4
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Umbrello Development Group
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-30 14:52 UTC by Jose N Hinckel
Modified: 2009-08-03 21:38 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
sample file with classes (141 bytes, text/plain)
2005-05-16 13:56 UTC, Jose N Hinckel 		Details
bugreport (2.74 KB, application/octet-stream)
2009-06-30 02:23 UTC, sunnychaos_75 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jose N Hinckel 2005-03-30 14:52:48 UTC 
Version:           1.4 (using KDE 3.4.0 Level "a" , SUSE 9.2 UNSUPPORTED)
Compiler:          gcc version 3.3.4 (pre 3.3.5 20040809)
OS:                Linux (i686) release 2.6.8-24.13-default

The code import fail when encounters a "\" for line continuation.
After removing continuation lines works normally
Comment 1 Jonathan Riddell 2005-05-15 13:21:26 UTC 
Could you give an example class please?
Comment 2 Jose N Hinckel 2005-05-16 13:56:25 UTC 
Created attachment 11058 [details]
sample file with classes

self-explaining example
Comment 3 sunnychaos_75 2009-06-30 02:23:10 UTC 
Created attachment 34927 [details]
bugreport
Comment 4 sunnychaos_75 2009-06-30 02:26:47 UTC 
umbrello everytime crashed at the end of an import.

first tried to import a whole projekt, then on .h-file.
I could see some "results" but umbrello allways crashed.

I use ubuntu 8.10 - gnome ??
Comment 5 FiNeX 2009-08-03 21:38:02 UTC 
@sunnychaos_75: please report your crash on a new bug report. this is specific to the given usecase. Remember to paste the backtrace and not attach it, remember also to install debug enabled packages. Read the following page for more informations:

http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports


@Jose: the bug is no more reproducible on KDE 4. It has been fixed :-)