[PATCH v2 3/3] gdb/python doc: Fix confusion between gdb.unwinders and gdb.unwinder

[Andrew Burgess]

Paulo Neves via Gdb-patches <gdb-patches@sourceware.org> writes:

> Replace gdb.unwinders with gdb.unwinder. The gdb.unwinders module does
> not and trying to import it leads to errors. Other instances of the
> manual correctly refer to gdb.unwinder.

This patch is fine.

Thanks,
Andrew

> ---
>  gdb/doc/python.texi | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
> index 444e332d752..59232750099 100644
> --- a/gdb/doc/python.texi
> +++ b/gdb/doc/python.texi
> @@ -2785,7 +2785,7 @@ class.  Derive your unwinder class from it and structure the code as
>  follows:
>  
>  @smallexample
> -from gdb.unwinders import Unwinder
> +from gdb.unwinder import Unwinder
>  
>  class FrameId(object):
>      def __init__(self, sp, pc):
> @@ -2828,7 +2828,7 @@ gdb.unwinder.register_unwinder (<locus>, MyUnwinder, replace=<True|False>)
>  An object file, a program space, and the @value{GDBN} proper can have
>  unwinders registered with it.
>  
> -The @code{gdb.unwinders} module provides the function to register a
> +The @code{gdb.unwinder} module provides the function to register a
>  unwinder:
>  
>  @defun gdb.unwinder.register_unwinder (locus, unwinder, replace=False)
> -- 
> 2.25.1