From: Andrew Cagney <ac131313@redhat.com>
To: Nick Roberts <nick@nick.uklinux.net>
Cc: gdb-patches@sources.redhat.com, bob_rossi@cox.net
Subject: Re: [rfc] Annotation level THREE
Date: Tue, 18 Mar 2003 16:00:00 -0000 [thread overview]
Message-ID: <3E774292.8070603@redhat.com> (raw)
In-Reply-To: <15990.62618.114706.459904@nick.uklinux.net>
>> > > The above list also contains thing like field-{begin,end},
> > > > array-section-{begin,end} et.al. Why are they needed.
> > >
> > > I use them to parse the output. They could probably go, if necessary, but
> > > others that you plan to take out *are* needed.
> >
> > Can you please be more specific?
>
> Perhaps I could turn that question round. Which annotations are you planning
> to keep?
I think annotations can be split into two categores:
- events
These let GDB notify the GUI of internal state changes.
- markups
These try to make CLI output, intended solely for a human, machine parsable.
The events remain (target changed, breakpoint created, ....). The
markups are removed (*-{begin,end})
Andrew
next prev parent reply other threads:[~2003-03-18 16:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 23:37 Andrew Cagney
2003-03-12 18:54 ` David Carlton
2003-03-12 19:04 ` Andrew Cagney
2003-03-14 0:08 ` Nick Roberts
2003-03-17 0:23 ` Andrew Cagney
2003-03-17 20:07 ` Nick Roberts
2003-03-17 20:38 ` Andrew Cagney
2003-03-18 10:31 ` Nick Roberts
2003-03-18 15:29 ` Andrew Cagney
2003-03-18 16:00 ` Andrew Cagney [this message]
2003-03-18 20:17 ` Bob Rossi
2003-03-12 6:09 Michael Elizabeth Chastain
2003-03-12 14:50 ` Andrew Cagney
2003-03-12 14:56 ` Daniel Jacobowitz
2003-03-12 17:04 ` David Carlton
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=3E774292.8070603@redhat.com \
--to=ac131313@redhat.com \
--cc=bob_rossi@cox.net \
--cc=gdb-patches@sources.redhat.com \
--cc=nick@nick.uklinux.net \
/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