From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [BUG:MI] -break-list doesn't list multiple breakpoints
Date: Wed, 30 Jan 2008 07:14:00 -0000 [thread overview]
Message-ID: <18336.7948.316240.708346@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200801300854.28358.ghost@cs.msu.su>
> > > > > 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. 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.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-01-30 6:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 22:08 Nick Roberts
2008-01-11 17:36 ` Vladimir Prus
2008-01-11 21:34 ` Nick Roberts
2008-01-11 22:55 ` Daniel Jacobowitz
2008-01-11 23:38 ` Nick Roberts
2008-01-15 17:08 ` Vladimir Prus
2008-01-15 21:38 ` Nick Roberts
2008-01-13 21:26 ` Nick Roberts
2008-01-29 19:16 ` Daniel Jacobowitz
2008-01-29 22:53 ` Nick Roberts
2008-01-29 23:31 ` Daniel Jacobowitz
2008-01-30 0:52 ` Nick Roberts
2008-01-30 3:04 ` Nick Roberts
2008-01-30 3:20 ` Daniel Jacobowitz
2008-01-30 5:59 ` Vladimir Prus
2008-01-30 7:14 ` Nick Roberts [this message]
2008-01-30 7:32 ` Vladimir Prus
2008-01-30 7:50 ` Nick Roberts
2008-01-30 7:58 ` Vladimir Prus
2008-02-01 20:15 ` Marc Khouzam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18336.7948.316240.708346@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox