Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [8/9] multiple locations
Date: Wed, 14 Nov 2007 19:18:00 -0000	[thread overview]
Message-ID: <18235.18919.959418.360780@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200711141047.03166.ghost@cs.msu.su>

 >...
 > I think the right approach would be moving the check for loc->shlib_disabled
 > later, like this:
 > 
 >     if (b->loc == NULL)
 >         ui_out_field_string (uiout, "addr", "<PENDING>");
 >     else if (header_of_multiple)
 >         ui_out_field_string (uiout, "addr", "<MULTIPLE>");
 >     else if (loc->shlib_disabled)
 >         ui_out_field_string (uiout, "addr", "<PENDING>");
 >     else
 >         ui_out_field_core_addr (uiout, "addr", loc->address);
 > 
 > But there's also testsuite to be updated and getting somebody to
 > actually approve this patch.

OK, but it looks much a smaller/simpler patch than the one you've already
committed.

 > >  > But generally, trying to keeping CLI back compatible have to stop
 > >  > at some time -- if we keep this "don't break CLI clients even if
 > >  > CLI clients were deprecated from some time" attitude, it will result
 > >  > in new features being available via MI only.
 > > 
 > > Focussing on the issue at hand, we're just talking about making a minor
 > > adjustment to the format of "info breakpoints", for the case of pending
 > > breakpoints, to avoid breaking existing frontend(s).  
 > 
 > Not quite. We're trying to please frontend(s) using deprecated protocol.
 > However little time is spent on that, it's time not spent on other, better
 > things.  Is there a reason Emacs website cannot say "Use MI support,
 > available at http://..."?

The short answer is that, although I have a mode that works with MI, it is
currently worse than the current one, which uses a mixture of MI and CLI
commands.  Even if it was as good, there would still be many people already
using Emacs 22.1 who wouldn't be aware of the website, or willing/able to
update Emacs from it.

Also MI is still evolving.  It's interesting that you suggest all frontends
should use it as the changes you have just made for breakpoints with
multiple locations appear in the output of "info breakpoints" but not
in that of "-break-list".  So I don't see how any front end could handle
this information through MI.

Unfortunately, the full transition to MI will be a slow one for Emacs.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2007-11-14 19:18 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13  7:15 Nick Roberts
2007-11-13  8:05 ` Vladimir Prus
2007-11-13  8:31   ` Nick Roberts
2007-11-13  8:45     ` Vladimir Prus
2007-11-13 12:38   ` Daniel Jacobowitz
2007-11-13 19:58     ` Vladimir Prus
2007-11-14 19:21       ` Jim Blandy
2007-11-13 22:20   ` Eli Zaretskii
2007-11-13 22:47     ` Joel Brobecker
2007-11-14  6:29       ` Vladimir Prus
2007-11-14  7:06         ` Nick Roberts
2007-11-14 11:58           ` Vladimir Prus
2007-11-14 19:18             ` Nick Roberts [this message]
2007-11-14 19:37               ` Joel Brobecker
2007-11-14 19:38               ` Vladimir Prus
2007-11-14 20:42                 ` Nick Roberts
2007-11-14 21:17                   ` Joel Brobecker
2007-11-15 20:39                   ` Vladimir Prus
2007-11-16 20:37                 ` Nick Roberts
2007-11-19  2:42                 ` Nick Roberts
2007-11-14 18:56         ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2007-09-07 22:49 Vladimir Prus
2007-09-07 22:51 ` Vladimir Prus
2007-09-08 11:46 ` Eli Zaretskii
2007-09-08 11:55   ` Vladimir Prus
2007-09-08 12:28     ` Eli Zaretskii
2007-09-22 19:53   ` Vladimir Prus
2007-09-23  4:13     ` Eli Zaretskii
2007-09-08 13:17 ` Mark Kettenis

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=18235.18919.959418.360780@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