This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] doc/gdbint.texinfo: memory allocation section
- To: nsd at redhat dot com
- Subject: Re: [RFA] doc/gdbint.texinfo: memory allocation section
- From: Eli Zaretskii <eliz at delorie dot com>
- Date: Thu, 14 Dec 2000 05:06:16 -0500 (EST)
- CC: gdb-patches at sources dot redhat dot com
- References: <200012132314.eBDNEto02097@rtl.cygnus.com>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> * gdbint.texinfo (Memory Allocation): New subsection.
>
> Okay to apply?
Thanks. This is approved, except for the following minor problems:
> +@itemize @bullet
> +@item The size parameter to @code{xmalloc}, @code{xcalloc}, and
> +@code{xrealloc} may be 0.
In an @itemize list, the @item needs to be alone on its line, like
this:
@item
The size parameter to @code{xmalloc}, @code{xcalloc}, and
@code{xrealloc} may be 0.
(It's true that `makeinfo' groks both formats, but that requires an
extra-special kludge in `makeinfo', which may one day be removed, and
it produces ugly results in HTML and DVI.)
Only in a @table you write the item's name immediately after @item.
> +by calling @code{alloca} when the stack is shallow. Toward that end,
> +each interface to the @value{GDBN} core --- for example, GDBTK, libgdb,
> +and the text console --- should ensure that @code{alloca (0)} is called
^^^^^
This should be @samp, not @code, since it's not a name of a symbol,
it's a code snippet.
> +periodically. In addition, @value{GDBN} calls @code{alloca (0)} once
^^^^^
And here.