background parser

[Mahmood Naderan]

>- What's your KDevelop version?
4.2.3

>- How many projects does your session have?
1

>- Do you remember if your session has crashed before?
yes, but after normal close and open the background parser works from 10 minutes
At first time after crash, I thought it si normal.

crashed->open kdevelop->background parser (10 min)->normal close->open
kdevelop->background parser (10min)


>- If you start KDevelop from the console, you'll see a lot of output
>while the background parser works. Do you see several lines saying
>ALREADY UP TO DATE?
yes a lot.

kdevelop(1604)/kdevelop (cpp support) CPPInternalParseJob::run: ===--
ALREADY UP TO DATE --===>
"/home/mahmood/gem5/build/X86_SE/debug/Event.hh"

kdevelop(1604)/kdevelop (cpp support) PreprocessJob::run:
PreprocessJob: preprocessing
"/home/mahmood/gem5/build/X86_SE/python/m5/internal/AddrRange_vector.i_init.cc"

kdevelop(1604)/kdevelop (cpp support)
IncludePathComputer::computeForeground: didn't get build manager for
project: "gem5"

kdevelop(1604)/kdevelop (cpp support)
IncludePathComputer::computeForeground: Did not find a build-manager
for KUrl("file:///home/mahmood/gem5/build/X86_SE/python/m5/internal/AddrRange_vector.i_init.cc")

kdevelop(1604)/kdevelop (cpp support)
IncludePathComputer::computeBackground: current include path
dependency state: "[/home/mahmood/gem5/.kdev_include_paths:13:01:02
(rev 1)]"

kdevelop(1604)/kdevelop (cpp support)
IncludePathComputer::computeBackground: Did not get any include-paths
for KUrl("file:///home/mahmood/gem5/build/X86_SE/python/m5/internal/AddrRange_vector.i_init.cc")

kdevelop(1604)/kdevelop (cpp support)
IncludePathComputer::computeBackground: took include-paths for
KUrl("file:///home/mahmood/gem5/build/X86_SE/python/m5/internal/AddrRange_vector.i_init.cc")
from duchain of
"/home/mahmood/gem5/build/X86_SE/python/m5/internal/param_NetworkTest_wrap.cc"

kdevelop(1604)/kdevelop (cpp support) CPPParseJob::mergeDefines:
DEFINES: QHash()

kdevelop(1604)/kdevelop (cpp support) CPPInternalParseJob::run: ===--
ALREADY UP TO DATE --===>
"/home/mahmood/gem5/build/X86_SE/python/m5/internal/AddrRange_vector.i_init.cc"

kdevelop(1604)/kdevelop (cpp support) PreprocessJob::run:
PreprocessJob: preprocessing
"/home/mahmood/gem5/build/X86_SE/cpu/BaseCPU.py.cc"

kdevelop(1604)/kdevelop (cpp support)
IncludePathComputer::computeForeground: didn't get build manager for
project: "gem5"

kdevelop(1604)/kdevelop (cpp support)
IncludePathComputer::computeForeground: Did not find a build-manager
for KUrl("file:///home/mahmood/gem5/build/X86_SE/cpu/BaseCPU.py.cc")

kdevelop(1604)/kdevelop (cpp support)
IncludePathComputer::computeBackground: current include path
dependency state: "[/home/mahmood/gem5/.kdev_include_paths:13:01:02
(rev 1)]"

kdevelop(1604)/kdevelop (cpp support)
IncludePathComputer::computeBackground: Did not get any include-paths
for KUrl("file:///home/mahmood/gem5/build/X86_SE/cpu/BaseCPU.py.cc")

kdevelop(1604)/kdevelop (cpp support)
IncludePathComputer::computeBackground: took include-paths for
KUrl("file:///home/mahmood/gem5/build/X86_SE/base/condcodes.hh") from
duchain of "/home/mahmood/gem5/build/X86_SE/base/socket.cc"

kdevelop(1604)/kdevelop (cpp support) CPPParseJob::mergeDefines:
DEFINES: QHash()


>However it still needs to check each file to see wether it needs to be
>reparsed or not, depending on the amount of files and access speed to
>them this can take more or less time
>But generally this is not a huge problem, since you can already work
>with KDevelop while this is running in the background

I agree with that because the src/ contains 2047 files. but isn't
there any way to reduce parser cpu usage?



On 12/5/11, Andreas Pakulat <apaku at gmx.de> wrote:
> On 05.12.11 11:17:48, Mahmood Naderan wrote:
>> Hi,
>> Every time I start kdevelop, the back ground parser work for about 10
>> minute. Isn't there anyway to cache?
>
> It already does, otherwise it would always take as much time as it did
> the first time you opened that project.
>
> However it still needs to check each file to see wether it needs to be
> reparsed or not, depending on the amount of files and access speed to
> them this can take more or less time.
>
> But generally this is not a huge problem, since you can already work
> with KDevelop while this is running in the background. Obviously you
> might not see new/changed things from files that haven't been re-parsed
> yet.
>
> Andreas
>
>
> _______________________________________________
> kdevelop mailing list
> kdevelop at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop
>


-- 
--
// Naderan *Mahmood;