From: Bob Rossi <bob@brasko.net>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Removal of markup annotations
Date: Wed, 15 Jun 2005 23:35:00 -0000 [thread overview]
Message-ID: <20050615233529.GC21803@white> (raw)
In-Reply-To: <17072.46112.23475.26195@farnswood.snap.net.nz>
On Thu, Jun 16, 2005 at 11:05:04AM +1200, Nick Roberts wrote:
> > Out of all of the annotations that you are removing here, CGDB only
> > depends on annotate_breakpoints_headers, annotate_field,
> > annotate_breakpoints_table, annotate_record and
> > annotate_breakpoints_table_end.
>
> These are undocumented annotations and just mark up the output. Could
> you parse it from the syntax instead?
These were documented when I wrote the CGDB annotation subsystem.
Between now and then, someone changed the documentation.
This link may work to demonstrate the fact.
http://web.archive.org/web/20030627071226/sources.redhat.com/gdb/current/onlinedocs/gdb_toc.html
I could look into parsing the syntax, but I would prefered if these
stayed. Is this not desirable for some reason?
> > I'll have to look deeper to verify this, but if this is true, it would
> > really simplify my life if we could leave those in. That at least would
> > allow CGDB to work with the next release of GDB while I work on
> > GDB/MI and getting CGDB to integrate with it.
>
> I've come to the conclusion that a fully working GDB/MI is a major task.
> Sorting out annotations could be done much more quickly.
I've been extremely busy. When I finish up some tasks, I'm going to
devote myself full time to this task. I would like nothing better than
to see CGDB work with a fully functional GDB/MI.
Bob Rossi
next prev parent reply other threads:[~2005-06-15 23:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 3:19 Nick Roberts
2005-06-15 15:41 ` Bob Rossi
2005-06-15 23:07 ` Nick Roberts
2005-06-15 23:35 ` Bob Rossi [this message]
2005-06-15 23:58 ` Nick Roberts
2005-06-21 1:41 ` Bob Rossi
2005-06-21 6:00 ` Nick Roberts
2005-06-21 10:22 ` Bob Rossi
2005-06-16 3:28 ` Eli Zaretskii
2005-06-15 17:06 ` Eli Zaretskii
2005-06-15 21:41 ` Nick Roberts
2005-06-20 11:54 ` Nick Roberts
2005-06-20 19:29 ` Eli Zaretskii
2005-06-20 21:48 ` Nick Roberts
2005-06-21 3:41 ` Eli Zaretskii
2005-06-21 7:32 ` Nick Roberts
[not found] ` <uacljzbgq.fsf@gnu.org>
2005-06-21 23:47 ` Nick Roberts
2005-06-22 3:25 ` Eli Zaretskii
2005-06-22 6:22 ` Nick Roberts
2005-07-03 19:04 ` Daniel Jacobowitz
2005-07-03 22:13 ` Nick Roberts
2005-07-03 22:45 ` Daniel Jacobowitz
2005-09-28 0:17 ` Nick Roberts
2005-09-28 2:39 ` Bob Rossi
2005-09-28 3:45 ` Daniel Jacobowitz
2005-09-28 6:40 ` Nick Roberts
2005-09-28 13:11 ` Daniel Jacobowitz
2005-09-28 22:52 ` Nick Roberts
2005-09-28 22:56 ` Daniel Jacobowitz
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=20050615233529.GC21803@white \
--to=bob@brasko.net \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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