Bug 63373

If you had reported the error like I said I wouldn't have to correct the 
KDevelop version by hand :( 
Please use Help->Report Bug to report future bugs 

I don't understand what you mean when you say "the highlighting of the current 
position in the debugged source does not work as well as the breakpoint 
position indication" What is the exact behaviour you see and what is it you are 
expecting to happen. 
 
Does it go to the right line of source? Or are we talking about the 
highlighting of the line only or...? 
 
Now, if we're talking about the highlighting then I believe it should work in 
the qteditor but not in the katepart editor. Which part are you using? 
 

Debugger goes to the right line of the source.

From Roger Larsson I have learned that the current program position in source
should be highlighted with the green colour and the line which the breakpoint is
set on should be highlighted by red. Well, I have not seen such behaviour yet. 

What it does for me is:

Using KATE:

press F6, the column left to the KATE window appears.

left click on the column left to the editor window sets bookmark. 

Right-click->toggle breakpoint sets breakpoint which I can see in the
breakpoints window only.

When debugger is fired, only cursor (that ordinary tiny pipe character) is
positioned on the left side of the current program position cource line. No
highlighting, no green triangle (which I am used to from KDevelop-2) )on the
left to the current line. It is impossible to be used.


Using Qt editor:

I have not known about it at all, sorry.

Left click left to the source line where I want to set breakpoint sets the
breakpoint - no line highlighting happens (should it at all or not ?)

When debugging, the green triangle left to the QtE shows the current program
position in the source.


Otherwise, the debugger does its job, except that I am not used to the gideon
build process and I do not exactly know when I build correctly and when not ...
but it is another story.


If the described behaviour is correct by you and for gideon (regarding the
Qt/KDE compatibility information on the kdevelop home page), please mark this
bug thread resolved or report to me to do it.

Good - now I understand :-) 
 
Kate part from kdelibs 3.0.x: 
This doesn't have good support for the debugger IIRC. I think what you are 
seeing is the "correct" behaviour for that version. 
 
Kate part from kdelibs 3.1.x: 
The highlight line for _debugging_ doesn't happen yet but the green triangle 
appears.Also whether debugging or not, the line the cursor is on is highlighted 
(in blue) which I find very useful.  
 
QTEditor 
I think for kdelibs 3.0.x this is the one to use. And there is no line 
highlighing. This is in kdevelop source so is independent of the kdelibs 
version (Hmm, is some of the code ifdef'd out because of library interface 
different?) 
 
If I were you I'd think hard about moving to kdelibs3.1. 
 
Also why not give the cvs version of kdevelop a try. Be careful that you remove 
the old kdevelop parts though. There has been a few emails that suggest that 
people have had some problems here without removing the old ones first. 
However, be warned that just at the moment things may not be as stable as 
normal due to the "mad hackers party" at Nove Hrady. One thing I really 
appreciate is the fast load of large projects when starting up, not to mention 
other features that have been added. 
 
I shall close this now :-) 
 

I've just been informed that now all KDevPlugins have versioning support in 
their .desktop file, so KDevelop won't try to load old plugins from a prior 
installation. 
 
Good news :-)