Re: [doc RFA] Move docs on auto-loading extensions to Extending GDB section

[Eli Zaretskii <eliz@gnu.org>]

> From: Doug Evans <xdje42@gmail.com>
> Cc: gdb-patches@sourceware.org
> Date: Mon, 23 Dec 2013 10:03:52 -0800
> 
> I did change/add *some* wording, but kept it minimal.
> E.g., I added this:
> 
> +There are various kinds of files @value{GDBN} can automatically load.
> +In addition to these files, @value{GDBN} supports auto-loading code written
> +in various extension languages. @xref{Auto-loading extensions}.
                                 ^^
Two spaces.

> >> +@menu
> >> +* objfile-gdb.ext file::         The @file{@var{objfile}-gdb.@var{ext}} file
> >
> > Node names cannot contain periods, this confuses some Info readers.
> 
> I guess the solution here is to use this?
> 
>      * MENU-ENTRY-NAME: NODE-NAME.   DESCRIPTION
> 
> [cut-n-pasted from texinfo docs]

Yes.

> If so, I'll use it for this entry too:
> 
> * dotdebug_gdb_scripts section:: The @code{.debug_gdb_scripts} section

Thanks.

> >> +For systems using file formats like ELF and COFF,
> >> +when @value{GDBN} loads a new object file
> >> +it will look for a special section named @code{.debug_gdb_scripts}.
> >> +If this section exists, its contents is a list of NUL-terminated names
> >                                                      ^^^
> > "NULL", right?
> 
> NULL is a zero-valued pointer.
> NUL is the common ASCII name for character '\0'.
> I grepped for other uses of NUL in the docs and found a few
> so figured it was ok to use.  E.g.,
> 
> ---snip---
> There is no trailing NUL byte in a remote protocol packet; if the stub
> stores packets in a NUL-terminated format, it should allow an extra
> byte in its buffer for the NUL.  If this stub feature is not supported,
> ---snip---

Unicode calls it NULL, but I won't argue.

Thank, you can commit the patch.