Version: kdevelop-3.2.0-1.0.rhel3.kde (using KDE KDE 3.4.0) Installed from: RedHat RPMs Compiler: gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-20) OS: Linux I cannot import and existing directory structure as a new project if it contains recursive links. When I try, kdevelop hangs and becomes unresponsive. An strace of the kdevelop pid shows never ending calls similar to: lstat64("/vobs/ltx_ui/optool/sun/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/include/vp_trig.hxx", {st_mode=S_IFREG|0444, st_size=7047, ...}) = 0 getdents64(14, /* 10 entries */, 8192) = 336 lstat64("/vobs/ltx_ui/optool/sun/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/include/vp_trig.ph", {st_mode=S_IFREG|0444, st_size=2125, ...}) = 0 lstat64("/vobs/ltx_ui/optool/sun/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/bld_tools/b I suggest there should be an import option to not follow simlinks or an advanced tab to skip things matching a regex.
By the way. Here is the package info on my version of kdevelop: rpm -qi kdevelop Name : kdevelop Relocations: (not relocateable) Version : 3.2.0 Vendor: The KDE-RedHat Project Release : 1.0.rhel3.kde Build Date: Sat 05 Mar 2005 02:08:20 PM EST Install Date: Mon 04 Apr 2005 11:48:41 AM EDT Build Host: mathstat.unl.edu Group : Development/Tools Source RPM: kdevelop-3.2.0-1.0.rhel3.kde.src.rpm Size : 40654762 License: GPL Signature : DSA/SHA1, Thu 10 Mar 2005 10:17:23 AM EST, Key ID efe4780cff6382fa Packager : kde-redhat Developers <http://kde-redhat.sf.net/> URL : http://www.kdevelop.org/ Summary : Integrated Development Environment for C++/C
I confirm this happening, my guess is the part that goes through the whole directory structure does not check for recursion and blindly enters all directory found in its path.
Recursive symlinks are bad and you shouldn't use them in your project IMHO. What type of project is this?
The project is a multi-million line OS for an ATE tester. Parts of the code base are pushing 20 years old. Whether I like them or not, sym links are legal in a unix file system - and all tools must be able to handle them.
And what type of project is it? (QMake, Automake, or Custom makefiles)
The project uses custom makefiles.
this seems fixed in recent kdevelop3 versions.