Debugger lacks gdb's functionallity !

[Iztok Kobal]

I am working on a big project where I have to mix the old code written 
in Modula-2 (linked into the .so's) with the C++ code.  And I've got 2 
questions:

1. When debugging, I have to make links to the M2 sources into the 
project tree for debugger to find them. Why KDevelop's debugger does not 
provide simple off-line (preferrably in the project options) input line 
for additional directories (gdb's -directory  option) ? It would be also 
be fine (since the source file type is already determined by its 
extension in the editor) to make the "set lang whatever" command when 
diving into the other-than-C++ language source.

2. Why KDevelop's debugger does not provide simple input line (at run 
time) or upgrade the debugger's watch-variable-input-line (via some 
prefix, e.g. > or something) to act as the ordinary command line to the 
gdb ? This would solve some problems that are not met when doing pure 
C++ as e.g. seting breakpoints on addresses instead on symbols, seting 
variables' values, expanding records and dereferencing references in M2 
(or whatever language's) way instead of using C++ syntax etc etc etc.


I am often annoyed with all bunch of the debugger shells (ddd, kdbg, 
XYZdbg) because at last I allways must use the ol' goody gdb itself !

I have posted the same message under different subject and nobody 
answered to it ! I would really like to konow the reasons for not leting 
the users to use complete gdb functionality !

-- 
Iztok Kobal