From: Eli Zaretskii <eliz@is.elta.co.il>
To: ac131313@cygnus.com
Cc: gdb@sources.redhat.com
Subject: Re: libGDB doco (for gdbint.texinfo)
Date: Thu, 19 Jul 2001 00:00:00 -0000 [thread overview]
Message-ID: <200107190700.KAA28551@is.elta.co.il> (raw)
In-Reply-To: <3B551EE6.3020500@cygnus.com>
> Date: Wed, 18 Jul 2001 01:30:14 -0400
> From: Andrew Cagney <ac131313@cygnus.com>
>
> Below is a quick update to``libgdb''.
Thanks!
> Let the comments, questions, .. begin :-)
Ack. See below.
> @chapter libgdb
>
> @section libgdb 1.0
We need a few @node's here and there, to make cross-references work
better in the on-line version.
> Since @code{libgdb} development is on-going, its architecture is still
> evolving. The following components have so far been identified:
>
> @itemize @bullet
> @item
> Observer - @file{gdb-events}.
> @item
> Builder - @file{ui-out}
> @item
> Event Loop - @file{event-loop}
> @item
> Query Library - @file{libgdb}
> @end itemize
I'm confused: this seems to say that libgdb is part of itself?
> @itemize @bullet
> @item
> The client registers itself as an observer of @code{libgdb}
There should be a period at the end of this sentence.
> through to the client controlled @code{gdb_stdout} et.al. streams. At
"et.al." should be written "et.@: al.@:" in Texinfo.
> @subheading Event Loop - @file{event-loop}
> @file{event-loop}, currently non- re-entrant
That should be "non-reentrant" or "non-re-entrant", I think.
next prev parent reply other threads:[~2001-07-19 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 22:31 Andrew Cagney
2001-07-19 0:00 ` Eli Zaretskii [this message]
2001-07-19 9:41 ` Andrew Cagney
[not found] ` <3405-Thu19Jul2001221226+0300-eliz@is.elta.co.il>
2001-07-25 19:30 ` 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=200107190700.KAA28551@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--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