From: Nick Roberts <nick@nick.uklinux.net>
To: Andrew Cagney <ac131313@redhat.com>
Cc: bob_rossi@cox.net, gdb@sources.redhat.com
Subject: Re: GDB/MI revisited
Date: Mon, 03 Mar 2003 20:44:00 -0000 [thread overview]
Message-ID: <15971.48556.869220.215035@nick.uklinux.net> (raw)
In-Reply-To: <3E63A84A.4030407@redhat.com>
> What about defining `level three' annotations as the event stuff from
> level two but with all the breakpoint et.al. markups removed?
I think this is a good idea if it doesn't mean too much extra work for you.
It would certainly create some breathing space. Perhaps you could be more
specific about al if you are planning to remove other annotations than
breakpoints-invalid e.g frames-invalid.
> Having the CLI generate event annotations is hardly different to having
> MI generate it's event messages.
Which annotations constitute the event annotations?
Nick
next prev parent reply other threads:[~2003-03-03 20:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 20:20 Nick Roberts
2003-02-26 16:21 ` Andrew Cagney
2003-02-28 21:35 ` Nick Roberts
2003-03-02 2:35 ` Andrew Cagney
2003-03-02 23:57 ` Nick Roberts
2003-03-03 1:04 ` Bob Rossi
2003-03-03 19:09 ` Andrew Cagney
2003-03-03 20:44 ` Nick Roberts [this message]
2003-03-04 0:12 ` Andrew Cagney
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=15971.48556.869220.215035@nick.uklinux.net \
--to=nick@nick.uklinux.net \
--cc=ac131313@redhat.com \
--cc=bob_rossi@cox.net \
--cc=gdb@sources.redhat.com \
/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