importing a project

[Andreas Pakulat]

On 07.01.07 20:23:09, datax wrote:
> Andreas Pakulat wrote:
> > On 07.01.07 16:23:30, datax wrote:
> >   
> >> Andreas Pakulat wrote:
> >>     
> >>> There's one last thing you can try: Run kdevelop inside gdb and when it
> >>> starts looping, i.e. a short while after finishing the
> >>> import-project-dialog, send it a SIGSTOP and when gdb allows you to
> >>> execute commands again run bt. Post the output of that here, it might
> >>> give us a hint which code loops.
> >>>   
> >>>       
> >> I usually use ddd and then click the interrupt button, and here is 
> >> KDevelop running under that scenario after it got to 50% and locked up 
> >> while parsing u-boot-1.1.6.
> >>     
> >
> > Ok. I tried to import this project into KDevelop3.3.5 from Debian
> > unstable and have the same hang. Seems to be reproducable, I'll build a
> > version from source in the next days and see what info I can get.
> >
> > The backtrace is not worth much because it doesn't show where in the
> > function it currently is due to missing debug symbols.
> >
> Thank you Andreas for looking into this. Obviously one can argue that a 
> project, even a well-behaved project might not import into KDevelop, but 
> no project should lock-up KDevelop.

Of course its not nice, but C and C++ are really complicated languages
and the use of macros complicate things even more. I don't know what
exactly makes kdevelop hang on the file I mention below, but it
certainly isn't "common" code (else we would have much more
parser-related bugreports).

The stdout output of kdevelop3.3 shows that its failing on the fat.c
file in fs/fat. So one option for you could be to temporary delete this
file and import the project after that. Then re-add the file and never
add it to the project. This is probably the only way for you to use this
project, as you don't want to or can't update your 3.3 version and there
won't be a 3.3.6 version of kdevelop AFAIK.

This has the drawback that certain functions won't use the code in that
file, but as its a custom makefile project you'd be using the
file-selector or filetree plugin for file-management anyway.

I'm cc'ing this to the kdevelop-devel list and append the fat.c file (for
ease of verification), so the people that lately worked on the KDevelop
parser can look at this if a fix is already comitted to 3.4.

Andreas

-- 
Don't you feel more like you do now than you did when you came in?