[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 168175] kDevelop hangs when importing existing project
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2008-08-03 15:29:36
Message-ID: 20080803152936.13996.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=168175         
apaku gmx de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |cpp-parser



------- Additional Comments From apaku gmx de  2008-08-03 17:29 -------
Looks very similar to what I have here  - one thread with a pretty deep stackframe. \
However here kdevelop takes all CPU during the parsing and isn't really locked. I've \
let it run know for 3 hours and it didn't finish parsing that project.

I can only guess that some of the C++ or C files throws the parser off. You could try \
to only import part of the project that you want to work on if thats possible.

Using kdevelop4 I was able to import the project as Kdevelop4 doesn't yet parse all \
project files after loading the project. As I don't know which file is the \
problematic - or even which subdir I can't say wether the C++ parser in KDevelop4 \
works better with the code-base.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs


[prev in list] [next in list] [prev in thread] [next in thread]