Crash on CMake project import
alonso schaich
alonsoschaich at gmx.de
Thu Aug 27 11:57:34 BST 2009
On Wednesday 26 August 2009 22:26:54 Jonas Widarsson wrote:
> 2009/8/26 Jonas Widarsson <jonas at widarsson.com>:
> > 2009/8/26 Andreas Pakulat <apaku at gmx.de>:
> >> Both projects import just fine here, looking at the crash reports
> >> suggests that your build of kdevelop is not up-to-date with svn, so I'd
> >> suggest to first try an update.
> >
> > I updated immediately when I hit the problem. I usually wouldn't
> > report a problem without making sure it exists.
> > Maybe a clean build will make a difference, I don't know. I'll try
> > that, and update first again.
> > I also use the PHP plugin, would you think it might interfere in some
> > way? I haven't updated that today, but yesterday or the day before I
> > did.
> > I'll try some more then.
>
> I updated kdevplatform and kdevelop and compiled them again without
> wiping out the build dir.
> and now it works. I don't know what made the difference. This time I
> tried generating a new project before importing my own.
> Strange.
>
> Well then, sorry for all the noise.
I don't know whether it's usefull, but i also get "crashes" while opening
kdevelop with an cmake project being loaded at start. i'm putting crash into
quotations since it's not really a crash but rather kdevelop seems to receive
SIGABRT - the easiest way to reproduce it ( for me ) is to delete the
$HOME/.kdevduchain directory before starting kdevelop which will hang up
during the loading process - not the actual project loading but the symbol
parsing or whatever happens in the second loading step ( after the progress
bar gets reset for the first time ) .
restarting kdevelop then works fine.
alonso
More information about the KDevelop
mailing list