Debugging within Kdevelop 1.2 - Feature request

[Rene M�rten]

i must say, that every other ide under windoof also debug's if i set breakpoints...

it is a good idea with the switching between breakpoints or not !


On Sat, 08 Jul 2000, you wrote:
> On Sun, 09 Jul 2000, you wrote:
> > Hi, ( Warning - my english is horrible )
> >
> > I would want to tell my opinion about the subject.
> >
> > I have to say I did not yet dig into the source code of Kdevelop to verify
> > my point or to modify the "run" command behaviour ( source code is too huge
> > :).
> >
> > The only way I can make the integrated debugger to work when setting
> > breakpoints
> > is by pressing the cute little "gear-wearing-sunglasses"
> > button. If I press the "run" button, the debugger does not start.
> >
> > Thus,  the "run" command don;t care about breakpoints.
> > I think it is a faulty design.
> >
> >
> > The behaviour of the run command should be:
> >
> > when  "Run" command issued;
> >      if there are breakpoints then
> >      {
> >            verify and recompile source files which have new breakpoints
> > then rebuild the app.
> >             start with the integrated debugger - or issue the "debug"
> > command instead...;
> >      }
> >      else just continue to run normally.
> >
> > Simple isn't it ?
> >
> > It is not clear how to start the integrated debugger correctly.
> > I didn't know I have to press on the cute little "gear-wearing-sunglasses"
> > icon button... until I pressed it at the right time.
> >
> > That's it.
> > Is somebody is kindly considering this missing behaviour of the "run"
> > command for the next version of Kdevelop ( 2.0 ?)
> 
> I disagree :-)
> 
> Sometimes I want to "run" sometimes I want to "debug", regardless of whether 
> breakpoints are set or not. Note that I may want to run under the debugger 
> _without_ having any breakpoints set, which means I must have a "debug" 
> button.
> 
> I think the problem is that my documentation isn't very good for the 
> debugger. I'll have to do better next time :(
> 
> >
> > Yes, I am starting to be lazy because Kdevelop is too near to the
> > perfection :)
> >
> > Other questions:
> > I would want somebody to tell me about the state of "code completion".
> > Where can I look for informations on the current Kdevlop's WorkInProgess ?
> 
> Current kdevelop2.0 is in cvs and is heavily under development (ie doesn't 
> work :-). There is no "code completion" code in there yet
> 
> >
> > thanks.
> >
> > regards,
> > Serge Lussier
-- 
Kind Regards Rene Märten
E-Mail: Delta_x at Codewizards.org
Buisness: rmaerte1 at visteon.com
Home:   http://www.codewizards.de/kcommander