Breakpoints

[Niko Sams]

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.
The DebugSession class I introduced works with multiple debug sessions.
Some UI for switching the sessions is needed, and gdb needs to support
it. (that would require more work)

Niko