Editing source while debugging
ghost at cs.msu.su
Sun Dec 31 09:17:10 UTC 2006
On Sunday 31 December 2006 03:29, Jens Dagerbo wrote:
> > > Simple solution : leave it as it is and add a "code changed, do you want
> > > to rebuild it?" when the user tries to resume the program beeing
> > > debugged. This should be enouth of a warning that future breakpoints
> > > might not be as accurate as possible.
> > Then, we'd need a way to ask Kate not to move markers corresponding to
> > breakpoints.
> .. which we cannot do. KTE doesn't offer us this option. In fact, there is no
> way we can differentiate between "The user added/removed a breakpoint" (which
> we want to handle) and "The user is typing so the markers are moving".
But I hope we can ask the interfaces to change for KDE4, can we?
> The only thing I can see us realistically handling is my second option: as
> soon as we detect typing in the active file when the debugger is running,
> flush all its breakpoints - all bets are off, nothing we knew about
> breakpoint positions is valid any longer.
I suppose the provided we flush breakpoints only in gdb, and leave KDevelop's
breakpoints alone, to be enabled on next debugger run, this might work.
More information about the KDevelop-devel