I have been using kdevelop for a day now with a clean 1.4.2fc3, and said problem hasn't reoccurred. I suppose it's safe to say that whatever was going on, can't be triggered by using 1.4.2fc3 alone. Stefaan