[BUG:MI] -break-list doesn't list multiple breakpoints
Vladimir Prus
ghost@cs.msu.su
Wed Jan 30 07:32:00 GMT 2008
Nick Roberts wrote:
> > > > > > 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.
>
> The manual doesn't state that the breakpoint number will be a integer.
The manual fails to state lots of things, so frontend naturally make various
assumptions.
> Without the file and line information, the frontend can't display
> breakpoint icons or display the relevant source in a window, which must be
> worse.
Given that such a change has a potential to totally break frontend,
I'm not sure we can talk in the abstract. If you send me the most
recent version of your patch, I can see if KDevelop will be happy,
or not.
- Volodya
More information about the Gdb-patches
mailing list