Debugger library

[Aleix Pol]

On Sun, Mar 15, 2009 at 5:04 PM, Niko Sams <niko.sams at gmail.com> wrote:

> >> The start might have to stay - as a way to say with which debugger the
> >> target should
> >> be started.
> >
> > Shouldn't this rather be a property of the "run configuration" (probably
> an
> > implicit thing, hidden from the user depending on the actual run type
> thats
> > being created).
> Hmm, currently this defined though IRun::setInstrumentor("xdebug"). But
> one C++ target should be run by different RunProviders (default, gdb,
> valgrind) - however
> not xdebug. A php target by default and xdebug.
> So we need an api to find the possible RunProviders for a target.
>
Well, for now we can have 1 Start action per debugger, don't you think?


>
>
> > > A solution could be a DebuggerUI-Plugin that implements an interface -
> > > that all debuggers can use.
> > > What do you think?
> > That could be a possibility, provide the common ui in a plugin, which is
> > based on some interfaces and controller's provided as libraries and the
> > actual debugger implementations just provide implementations for those
> > interfaces...
> I'll come up with patches....
>
> Niko
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20090315/a7f22e43/attachment.html>