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

Vladimir Prus
2008-01-30T05:55:04Z

On Wednesday 30 January 2008 06:06:14 Daniel Jacobowitz wrote:
> On Wed, Jan 30, 2008 at 02:56:36PM +1300, Nick Roberts wrote:
> > > > 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.
>
> Xcode has a better one; I think they have breakpoint notifications.
>
> > 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.
>
> > > > 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.
> >
> > It won't break Emacs becuase it doesn't use the output of -break-insert.
>
> If the new output from -break-list works OK, that is.

It would be nice to actually *see* the examples of that new output ;-)
My theory (and why I did not implemented that for MI), is that frontends
will start showing breakpoint locations as if they were individual
breakpoint which is likely will fail. To begin with, if frontend uses integer
to represent breakpoint id, then "1.1" location id won't be representable.

- Volodya