Breakpoints

[Aleix Pol]

On Wed, Apr 15, 2009 at 6:41 PM, Vladimir Prus <ghost at cs.msu.su> wrote:

> On Wednesday 15 April 2009 14:25:13 Andreas Pakulat wrote:
> > On 15.04.09 13:06:38, Vladimir Prus wrote:
> > > On Wednesday 15 April 2009 11:10:17 Andreas Pakulat wrote:
> > >
> > > > > > > We technically can have a single list (as soon as we know
> > > > > > > breakpoint->config association internally for the benefit of
> 'sync' state
> > > > > > > display).
> > > > > >
> > > > > > Why is there a breakpoint->config association?
> > > > >
> > > > > Because config is the entity that sets breakpoints, and it should
> be
> > > > > able to distinguish between:
> > > >
> > > > Hmm, isn't it rather the debugger that sets it.
> > > >
> > > > >   - Breakpoints that must be inserted, and are inserted
> > > > >   - Breakpoints that must be inserted and are not, for any reason
> > > > >   - Breakpoints that are irrelevant
> > > > >
> > > > > In particular, display of  breakpoint in the breakpoint widget will
> > > > > be decorated with different icons depending on which of the above
> > > > > states is true.
> > > >
> > > > But I don't see why you'd need to know the config for doing that.
> > >
> > > Well, I hope you'll agree that we need some mechanism of understanding
> > > what breakpoints are irrelevant for the current debug session.
> >
> > If you meant to say "current debug sessions" (i.e. plural form) then yes
> I
> > agree.
>
> Whilst I believe the plural form is a can of worms that better not be
> opened,
> the mechanism are the same regardless of whether one or multiple debug
> sessions are allowed.
>
> > > > > 2. Launcher having to decide, using flaky heuristics, if a
> breakpoint
> > > > > "belongs" to it and should be inserted, or, alternatively, trying
> > > > > to insert all breakpoints.
> > > >
> > > > Then how do you imagine that the user explains KDevelop which
> breakpoint
> > > > should be used with which config?
> > >
> > > We'll have current launch config -- we already have it, and other IDEs
> have
> > > it too. Newly added breakpoints are associated with the current launch
> config.
> >
> > No, we have a "default run", which is executed if you don't choose a
> > different one. But if I debug two applications at the same time, I don't
> > want to have to switch the "current launch config" each time something
> > happens in the other app.
>
> How often do you debug two applications at the same time?
>
> > Also I don't see this being needed at all, a debug plugin, when starting
> an
> > app, can see _all_ breakpoints that have ever been set by the user. It
> can
> > then try to set all of them,
>
> And then will get errors setting half of them, and will display breakpoints
> as problematic in breakpoint widget, and users will wonder what broke.
>
> Anyway, it seems like we're not getting closure via email -- can we
> schedule
> a real time chat -- say IRC or Skype?
>

> - Volodya
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>

We could have some IRC meetings next week (when we're in the actual meeting)
so that we can talk those things all together even if people can't come.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20090415/f90b1cd8/attachment.html>