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 20:42:00 -0000 [thread overview]
Message-ID: <18235.23944.432662.13480@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200711142238.06000.ghost@cs.msu.su>
>...
> > OK, but it looks much a smaller/simpler patch than the one you've already
> > committed.
>
> Yes, but I have better luck getting huge patches approved, than for
> obvious patches, for whatever reasons.
>
> Basically, it boils down to:
> 1. Using <PENDING> like above seems a good idea to try.
> 2. There's a bit of time involved
> 3. I'm short of time, and probably won't spend it until all the
> patches I've sent already are reviewed ;-)
There's no hurry. It could be added to the Wiki as a TODO item for
GDB 6.8 Release.
Joel,
Can I do that just by creating an account? Shall I delete the GDB 6.7
Release page too?
> > 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.
> Heh, you probably know what's going on here yourself. Even though MI was
> advertised as the right interface for frontend for some years, it does not
> have a maintainer, or a particular development plan, and misses some bits.
> And probably the only way to change the situation is to decide that MI is
> the future, and actively discourage use of CLI for anything, to the degree
> of immediately refusing any request mentioning CLI in relation to any
> frontend.
I don't know why you insist on being so confrontational, or how the above lack
of support for MI is solved in any way by refusing requests for CLI, but I find
it quite unhelpful.
> As for multiple breakpoints -- I would have being happy to provide MI
> interface, and not provide CLI at all -- but I doubt that would have being
> acceptable, and MI has fallen out. Again, a policy that new advanced
> functionality is allowed to be available via MI only might have helped.
Presumably CLI is still needed by those who use GDB from the command line.
Or are you proposing to `help' them by forcing them to use a frontend?
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2007-11-14 20:42 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
2007-11-14 19:37 ` Joel Brobecker
2007-11-14 19:38 ` Vladimir Prus
2007-11-14 20:42 ` Nick Roberts [this message]
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.23944.432662.13480@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