This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [1/2] Inspect extra signal information
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Pedro Alves <pedro at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 02 Feb 2009 23:04:34 +0200
- Subject: Re: [1/2] Inspect extra signal information
- References: <200901121846.51709.pedro@codesourcery.com> <200901121852.06948.pedro@codesourcery.com> <u4p04co0y.fsf@gnu.org> <200902021652.28152.pedro@codesourcery.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Mon, 2 Feb 2009 16:52:27 +0000
>
> > I think this introduces a general-purpose infrastructure that must be
> > documented in gdbint.texinfo.
> >
>
> I'm taking a stab at this.
Thanks!
> I don't see struct value documented in
> the internals manual though. What kind of detail do you require here?
Exactly the kind you described.
> I'm thinking of adding a "Values" section somewhere, don't know
> where yet.
The place doesn't matter much, since the internals manual is "work in
progress", and looks more like a car crash than a concise document.
> @item @code{lval_computed}
>
> These are values with arbitrary functions to handle reads and writes,
Please lose the empty line between the @item and its description.
> and "copy operators" and "destructors". They allow creating
Please use ``this kind of quoting'' in Texinfo, not "this kind".
> described by the @code{struct lval_funcs} struture declared in
^^^^^^^^
A typo.
> @file{value.h} to the @code{allocate_computed_value} function. An
What does it mean "declared in value.h to the allocate_computed_value
function"?
Perhaps add a few words describing `struct lval_funcs', or maybe just
showing a simple example would be enough.
A couple of index entries for this section will also help.
Thanks again for working on this.