Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Matt Rice <ratmice@gmail.com>
To: gdb-patches@sourceware.org
Subject: [patch][python][doc] PR 12918 reference decode_line in py SAL docs.
Date: Sat, 02 Jul 2011 14:20:00 -0000	[thread overview]
Message-ID: <CACTLOFq0ObmbtAKPrss3UMoHvGzNAbC+3bfYwaOyi6OUb6muYQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 254 bytes --]

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.

[-- Attachment #2: foo.diff --]
[-- Type: application/octet-stream, Size: 752 bytes --]

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.

             reply	other threads:[~2011-07-02 14:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-02 14:20 Matt Rice [this message]
2011-07-02 17:00 ` Eli Zaretskii
2011-07-02 21:54   ` Matt Rice
2011-07-03  2:58     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACTLOFq0ObmbtAKPrss3UMoHvGzNAbC+3bfYwaOyi6OUb6muYQ@mail.gmail.com \
    --to=ratmice@gmail.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox