[patch][python][doc] PR 12918 reference decode_line in py SAL docs.
Eli Zaretskii
eliz@gnu.org
Sat Jul 2 17:00:00 GMT 2011
> Date: Sat, 2 Jul 2011 07:20:08 -0700
> From: Matt Rice <ratmice@gmail.com>
>
> here is an attempt at 12918, along with the original reporter,
> I also had overlooked the decode_line method.
>
> 2011-07-02 Matt Rice <ratmice@gmail.com>
>
> * gdb.texinfo (Symbol Tables In Python): Add reference to the
> decode_line function.
>
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index dbaf30e..cbfaddd 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -23258,7 +23258,9 @@ Access to symbol table data maintained by @value{GDBN} on the inferior
> is exposed to Python via two objects: @code{gdb.Symtab_and_line} and
> @code{gdb.Symtab}. Symbol table and line data for a frame is returned
> from the @code{find_sal} method in @code{gdb.Frame} object.
> -@xref{Frames In Python}.
> +@xref{Frames In Python}. Symbol table and line data for an arbitrary
> +linespec is returned from the @code{decode_line} function.
> +@xref{Basic Python}.
>
> For more information on @value{GDBN}'s symbol table management, see
> @ref{Symbols, ,Examining the Symbol Table}, for more information.
Thanks, but how does this address the PR? This is the full text of
PR 12918:
There is no (obvious) documented way to get a symtab_and_line object given an
arbitrary address.
A function gdb.sal_for_pc() similar to gdb.block_for_pc() would be nice.
If you want to tell that decode_line is the answer for the PR's
request, then why not update the documentation of decode_line, which
is almost 2000 lines earlier in the manual and in a different node?
IOW, why are you adding this text in this particular place?
Sorry if I'm missing something obvious.
More information about the Gdb-patches
mailing list