Version: 3.0.0 (using KDE KDE 3.2.0) Installed from: Gentoo Packages Compiler: gcc 3.3.2 OS: Linux When I try to import a project and specify Custom C++ with Automake, KDevelop will crash, unless I specify an Author's name (anything, but an empty string). Here is the backtrace: (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 20386)] [New Thread 32769 (LWP 20396)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 20386)] [New Thread 32769 (LWP 20396)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 20386)] [New Thread 32769 (LWP 20396)] 0x4168504b in waitpid () from /lib/libpthread.so.0 #0 0x4168504b in waitpid () from /lib/libpthread.so.0 #1 0x40dd8bec in __JCR_LIST__ () from /usr/kde/3.2/lib/libkdecore.so.4
Can't reproduce. The backtrace is useless, so there is nothing to go by except the bug description and I have no problem importing projects as "Generic C++ Application (Automake based)".
I do realize the backtrace is useless, could give me some quick guidelines on how to make it produce the real core file and not this KCrash rubish? Then i might try to debug it myself.
Can I 2nd Sergey Kuleshov's comment on - how to get a real core file or stack trace. Is there anything on the web; tutorial, How-To, anything that we could be pointed to? I am having similar problems and would like to have real information to report.
"export KDE_DEBUG=1" should do it according to the Developer FAQ: http://developer.kde.org/documentation/other/developer-faq.html#q3.1 But to really be able to do any reasonable debugging you'll need the debugging symbols compiled into the executable, and if you have this, the KDE crash dialog should also be able to give you a good backtrace.
Follow the instructions on the top of: http://www.kdevelop.org/index.html?filename=branches_compiling.html and get yourself a debug-enabled system.
I've run across the same problem, although I don't think the author's name is significant. (I've filled it in and kdevelop crashes just as much). The project I'm trying to import is http://sourceforge.net/projects/foxdialogeditor/ To reproduce to a CVS checkout, and try to import the project into kdevelop. The model was C++ automake.
I tried to import the project. The sourceforge cvs server won't let me in. "cvs [login aborted]: end of file from server" Anyway, I seriously doubt it's related to this specific project. "cryst", you don't specify your distro, but the original reporter is on "gentoo packages", which means this whole thing is probably a dupe of bug #73346. (Unless a backtrace proves it, I refuse to believe the crash is related to neglecting to state an author in the import box.) (The common case of this bug should be removed simply by remerging KDevelop, as the latest Gentoo package does not have the patch.)
Well, fyi I'm also on gentoo. I just included the project to show how I was able to create the error. Thanks for taking the time to point out that the bug appears gentoo specific.
OK. Thanks for the feedback. Assuming dupe. *** This bug has been marked as a duplicate of 73346 ***