RE: [BUG:MI] -break-list doesn't list multiple breakpoints

Marc Khouzam
2008-02-01T20:15:50Z

>> > > It's a backwards incompatible change but do other frontends use it?
>> >
>> > Yes; I checked Eclipse before I wrote back.
>>
>> That's odd because ISTR that Eclipse has a console. What happens if you
>> create a breakpoint from the command line? Perhaps Marc can comment.
>
>The console is fairly limited.
>
>> Also isn't DSF meant to replace the debugger frontend that is currently part of
>> Eclipse CDT?
>
>I don't think that's certain yet.

The current discussed plan is to offer both CDI (current CDT debugger frontend) and
DSF, in the next CDT release. It is not official but we are aiming for that.
From what I gather, both will be supported for while.

From a DSF perspective, the breakpoint handling was just recently finished.
And from what I see, the detailed output of break-insert is being used.
This is also true for CDI.

As for the console, I not sure what the ultimate goal is...
When I tried setting a breakpoint from the console it did not trigger any
reaction in the UI. I'll follow up on this within DSF.

> > > As an alternative, I guess this line alone could be removed so that
> > > -break-insert lists the multiple breakpoint locations being set and the
> > > adjust MI documentation to explain this.
> >
> > We should check what the new MI output looks like, and see if it
> > breaks Emacs / Eclipse / Kdevelop. It might be that easy.

I'm guessing from the beginning of the thread, that the output will only only
change in the case of template functions? Is that right?
If that is the case, we don't have a testcase for that :-)
I'll follow up with this too.

Marc