This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] PR python/12438
- From: Eli Zaretskii <eliz at gnu dot org>
- To: pmuldoon at redhat dot com
- Cc: tromey at redhat dot com, gdb-patches at sourceware dot org
- Date: Thu, 07 Jul 2011 20:38:20 +0300
- Subject: Re: [patch] PR python/12438
- References: <m31uyblkwj.fsf@redhat.com> <m3vcvndrci.fsf@fleche.redhat.com> <m3liwarryf.fsf@redhat.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Phil Muldoon <pmuldoon@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Thu, 07 Jul 2011 17:11:36 +0100
>
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -20801,10 +20801,16 @@ End with a line saying just "end".
>
> @kindex maint set python print-stack
> @item maint set python print-stack
> -By default, @value{GDBN} will print a stack trace when an error occurs
> -in a Python script. This can be controlled using @code{maint set
> -python print-stack}: if @code{on}, the default, then Python stack
> -printing is enabled; if @code{off}, then Python stack printing is
> +This command is now deprecated. Instead use @code{set python
> +print-stack} (@pxref{set python print-stack}).
> +
> +@kindex set python print-stack
> +@item set python print-stack
> +@anchor{set python print-stack}
> +By default, @value{GDBN} will not print a stack trace when an error
> +occurs in a Python script. This can be controlled using @code{set
> +python print-stack}: if @code{on}, then Python stack printing is
> +enabled; if @code{off}, the default, then Python stack printing is
> disabled.
> @end table
Thanks. This part is okay, but please lose the @pxref and the anchor,
because the referenced part is just one line away. Instead, say
something like "..., described below."