Version: unknown (using KDE Devel) Installed from: Compiled sources Compiler: gcc version 3.3.1 (SuSE Linux) OS: Linux (i686) release 2.4.19-4GB When I read the API/architecture documentation I remembered one thing I saw earlier but did not report. Since I am currently recompiling KDE I can not check if this works in recent releases. So I report it here most as a mental note. (The API documentation: http://developer.kde.org/documentation/library/cvs-api/kdevelop/html/architecture.html ) And noticed that GDB debug is a subdirectory of C/C++ But GDB could also be used for Fortran, ADA, ... Even worse is that Java can be compiled with gcj http://gcc.gnu.org/java/ and that result should be debugged with GDB... Some restructuring is needed...
This is know. The problem was introduced in b1 by me. I and some other persons in the project got the idea that the degugger could only do C. jbb corrected me but I haven't corrected the problem yet because he didn't told me exacly which languages (from the 12 KDevelop supports) GDB supports. He also have a Java debugger. What should we do with it?
Simple rule - gdb can debug everything (close enough)... Debug should be a subsystem on its own! ("Debug Tools") Then you can select the debug system you like - gdb, ddd, ..., java debug. Note the case where gdb can be used to debug natively compiled java programs. source in java compile to bytecode (no link?) debug with java debugger compile to object code with gcj link with ... debug with gcc debug with ddd
(tabs was deleted in previous...) Almost forgot - in one project the source code type can be mixed!
this will change in kdevelop4, but hasn't been finished yet.
does the kdevelop4 gdb plugin have any c++ dependencies? I don't think so. At least it's not under a c++ directory anymore.
No, it's not linking against the c++ module.
right, it doesn't use C++ support and AFAIK never did - even though it was in the cpp subdir. closing as invalid