From: Doug Evans <dje@google.com>
To: Siva Chandra <sivachandra@google.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [RFC] - Exposing find_pc_line through Python API
Date: Thu, 10 May 2012 21:16:00 -0000 [thread overview]
Message-ID: <CADPb22TvTO=1FEDPMORYUG8kOfvshf9jzW2g_ycN_QWNN7OhUg@mail.gmail.com> (raw)
In-Reply-To: <CAGyQ6gwkpvLwhO_gEcEtQFEND_A+fk5ive6qgFfBqgTn4fa_0w@mail.gmail.com>
On Wed, May 9, 2012 at 12:35 AM, Siva Chandra <sivachandra@google.com> wrote:
> The more I think about your comments, the more I feel that exposing
> this 'actual' argument is not a good idea. I am now of the opinion
> that the 'notcurrent' argument to the internal function find_pc_line
> caters to a internal usage which depends on much more than just what
> the user feels. Hence, I have modified the patch to remove the
> 'actual' argument. The new version of the patch is attached.
>
> 2012-05-07 Siva Chandra Reddy <sivachandra@google.com>
>
> Add a new function gdb.find_pc_line to the Python API.
> * NEWS (Python Scripting): Add entry about the new function.
> * python/python.c (gdbpy_find_pc_line): New function which
> implements gdb.find_pc_line.
> (GdbMethods): Add entry for the new function.
>
> doc/
> * gdb.texinfo (Basic Python): Add description about the function
> gdb.find_pc_line
>
> testsuite/
> * gdb.python/python.c: Add a new breakpoint comment.
> * gdb.python/python.exp: Add tests to test gdb.find_pc_line.
+@findex gdb.find_pc_line
+@defun gdb.find_pc_line (pc)
+Return the @code{gdb.Symtab_and_line} object corresponding to the
+@var{pc} value. @xref{Symbol Tables In Python}.
+@end defun
I think we need to specify what the result is if there is no sal for
the specified pc.
+/* Implementation of gdb.find_pc_line function.
+ Returns the gdb.Symtab_and_line object corresponding to a PC value. */
+
+static PyObject *
+gdbpy_find_pc_line (PyObject *self, PyObject *args)
+{
+ struct symtab_and_line sal;
+ CORE_ADDR pc;
+ unsigned long long pc_llu;
+ PyObject *actual = NULL;
+
+ if (!PyArg_ParseTuple (args, GDB_PY_LLU_ARG, &pc_llu))
+ return NULL;
+
+ pc = (CORE_ADDR) pc_llu;
+ sal = find_pc_line (pc, 0);
+ return symtab_and_line_to_sal_object (sal);
+}
"actual" can be deleted now.
next prev parent reply other threads:[~2012-05-10 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 18:11 Siva Chandra
2012-05-07 19:36 ` Eli Zaretskii
2012-05-08 2:35 ` Siva Chandra
2012-05-09 7:35 ` Siva Chandra
2012-05-09 20:05 ` Eli Zaretskii
2012-05-10 21:16 ` Doug Evans [this message]
2012-05-11 16:35 ` Siva Chandra
2012-05-11 18:14 ` Doug Evans
2012-05-13 11:37 ` Siva Chandra
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='CADPb22TvTO=1FEDPMORYUG8kOfvshf9jzW2g_ycN_QWNN7OhUg@mail.gmail.com' \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=sivachandra@google.com \
/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