From: Jan Vrany <jan.vrany@labware.com>
To: gdb-patches@sourceware.org
Cc: Jan Vrany <jan.vrany@labware.com>, Eli Zaretskii <eliz@gnu.org>
Subject: [RFC v5 16/18] gdb/python: allow instantiation of gdb.LineTableEntry objects
Date: Mon, 23 Jun 2025 17:10:11 +0100 [thread overview]
Message-ID: <20250623161013.650814-17-jan.vrany@labware.com> (raw)
In-Reply-To: <20250623161013.650814-1-jan.vrany@labware.com>
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
---
gdb/doc/python.texi | 8 ++++
gdb/python/py-linetable.c | 52 +++++++++++++++++++----
gdb/testsuite/gdb.python/py-linetable.exp | 25 +++++++++++
3 files changed, 77 insertions(+), 8 deletions(-)
diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
index 7c3a87cdaad..2b33cd32201 100644
--- a/gdb/doc/python.texi
+++ b/gdb/doc/python.texi
@@ -6839,6 +6839,14 @@ True if pc (associated with this entry) marks the start of the epilogue.
This attribute is not writable.
@end defvar
+@code{LineTableEntry} objects have the following methods:
+
+@defun LineTableEntry.__init__ (line, pc@r{[}, is_stmt@r{][}, prologue_end@r{][}, epilogue_begin@r{]})
+Create new line table entry. Arguments correspond to @code{LineTableEntry}
+attributes described above. Optional arguments @var{is_stmt},
+@var{prologue_end} and @var{epilogue_begin} default to @code{False}.
+@end defun
+
As there can be multiple addresses for a single source line, you may
receive multiple @code{LineTableEntry} objects with matching
@code{line} attributes, but with different @code{pc} attributes. The
diff --git a/gdb/python/py-linetable.c b/gdb/python/py-linetable.c
index 5eb40bf3c5b..57d1a74bf78 100644
--- a/gdb/python/py-linetable.c
+++ b/gdb/python/py-linetable.c
@@ -146,7 +146,7 @@ build_line_table_tuple_from_entries (
for (i = 0; i < entries.size (); ++i)
{
- auto entry = entries[i];
+ const linetable_entry *entry = entries[i];
gdbpy_ref<> obj (build_linetable_entry (
entry->line, entry->pc (objfile), entry->is_stmt,
entry->prologue_end, entry->epilogue_begin));
@@ -390,6 +390,41 @@ ltpy_entry_get_epilogue_begin (PyObject *self, void *closure)
Py_RETURN_FALSE;
}
+/* Object initializer; creates new linetable entry.
+
+ Use: __init__(LINE, PC, IS_STMT, PROLOGUE_END, EPILOGUE_BEGIN). */
+
+static int
+ltpy_entry_init (PyObject *zelf, PyObject *args, PyObject *kw)
+{
+ linetable_entry_object *self = (linetable_entry_object *) zelf;
+
+ static const char *keywords[] = { "line", "pc", "is_stmt", "prologue_end",
+ "epilogue_begin", nullptr };
+ int line = 0;
+ CORE_ADDR pc = 0;
+ int is_stmt = 0;
+ int prologue_end = 0;
+ int epilogue_begin = 0;
+
+ if (!gdb_PyArg_ParseTupleAndKeywords (args, kw, "iK|ppp",
+ keywords,
+ &line,
+ &pc,
+ &is_stmt,
+ &prologue_end,
+ &epilogue_begin))
+ return -1;
+
+ self->line = line;
+ self->pc = pc;
+ self->is_stmt = is_stmt == 1 ? true : false;
+ self->prologue_end = prologue_end == 1 ? true : false;
+ self->epilogue_begin = epilogue_begin == 1 ? true : false;
+
+ return 0;
+}
+
/* LineTable iterator functions. */
/* Return a new line table iterator. */
@@ -604,12 +639,12 @@ static gdb_PyGetSetDef linetable_entry_object_getset[] = {
"The line number in the source file.", NULL },
{ "pc", ltpy_entry_get_pc, NULL,
"The memory address for this line number.", NULL },
- { "is_stmt", ltpy_entry_get_is_stmt, NULL,
- "Whether this is a good location to place a breakpoint for associated LINE.", NULL },
- { "prologue_end", ltpy_entry_get_prologue_end, NULL,
- "Whether this is a good location to place a breakpoint after method prologue.", NULL },
- { "epilogue_begin", ltpy_entry_get_epilogue_begin, NULL,
- "True if this location marks the start of the epilogue.", NULL },
+ { "is_stmt", ltpy_entry_get_is_stmt, nullptr,
+ "Whether this is a good location to place a breakpoint for associated LINE.", nullptr },
+ { "prologue_end", ltpy_entry_get_prologue_end, nullptr,
+ "Whether this is a good location to place a breakpoint after method prologue.", nullptr },
+ { "epilogue_begin", ltpy_entry_get_epilogue_begin, nullptr,
+ "True if this location marks the start of the epilogue.", nullptr },
{ NULL } /* Sentinel */
};
@@ -650,6 +685,7 @@ PyTypeObject linetable_entry_object_type = {
0, /* tp_descr_get */
0, /* tp_descr_set */
0, /* tp_dictoffset */
- 0, /* tp_init */
+ ltpy_entry_init, /* tp_init */
0, /* tp_alloc */
+ PyType_GenericNew, /* tp_new */
};
diff --git a/gdb/testsuite/gdb.python/py-linetable.exp b/gdb/testsuite/gdb.python/py-linetable.exp
index 40afd8c400e..cf01a694070 100644
--- a/gdb/testsuite/gdb.python/py-linetable.exp
+++ b/gdb/testsuite/gdb.python/py-linetable.exp
@@ -81,3 +81,28 @@ gdb_test "python print(lt.has_line(44))" \
gdb_test "python print(lt.has_line(10))" \
"False.*" \
"test has_pcs at line 10"
+
+# Test gdb.LineTableEntry.__init__ ()
+gdb_test "python print( gdb.LineTableEntry(10, 0xcafe0000).line)" \
+ "10" \
+ "test new LineTableEntry line"
+
+gdb_test "python print( gdb.LineTableEntry(10, 123456).pc)" \
+ "123456" \
+ "test new LineTableEntry pc"
+
+gdb_test "python print( gdb.LineTableEntry(10, 123456).is_stmt)" \
+ "False" \
+ "test new LineTableEntry is_stmt"
+gdb_test "python print( gdb.LineTableEntry(10, 123456).prologue_end)" \
+ "False" \
+ "test new LineTableEntry prologue_end"
+gdb_test "python print( gdb.LineTableEntry(10, 123456).epilogue_begin)" \
+ "False" \
+ "test new LineTableEntry epilogue_begin"
+gdb_test "python print( gdb.LineTableEntry('xx', 123456).pc)" \
+ "TypeError.*:.*" \
+ "test creating invalid gdb.LineTableEntry"
+gdb_test "python print( gdb.LineTableEntry(10, 123456, prologue_end = True).prologue_end)" \
+ "True" \
+ "test prologue_end keyword argument"
--
2.47.2
next prev parent reply other threads:[~2025-06-23 16:14 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 16:09 [RFC v5 00/19] Add Python "JIT" API Jan Vrany
2025-06-23 16:09 ` [RFC v5 01/18] gdb: introduce expand_symtabs_maybe_overlapping Jan Vrany
2025-06-24 15:22 ` Tom Tromey
2025-06-26 15:05 ` Jan Vraný
2025-06-23 16:09 ` [RFC v5 02/18] gdb: introduce compunit_symtab::maybe_contains Jan Vrany
2025-06-23 16:09 ` [RFC v5 03/18] gdb: update is_addr_in_objfile to support "dynamic" objfiles Jan Vrany
2025-06-23 16:09 ` [RFC v5 04/18] gdb: introduce new function create_function_type Jan Vrany
2025-06-24 15:29 ` Tom Tromey
2025-06-26 11:12 ` Jan Vraný
2025-06-27 14:21 ` Tom Tromey
2025-06-27 14:30 ` Jan Vraný
2025-06-23 16:10 ` [RFC v5 05/18] gdb/python: add function () method to gdb.Type object Jan Vrany
2025-06-24 16:11 ` Tom Tromey
2025-06-26 11:13 ` Jan Vraný
2025-06-23 16:10 ` [RFC v5 06/18] gdb: use std::vector<> to hold on blocks in struct blockvector Jan Vrany
2025-06-23 16:10 ` [RFC v5 07/18] gdb/python: add gdb.Compunit Jan Vrany
2025-06-23 16:10 ` [RFC v5 08/18] gdb/python: allow instantiation of gdb.Objfile from Python Jan Vrany
2025-06-23 16:10 ` [RFC v5 09/18] gdb/python: add unlink () method to gdb.Objfile object Jan Vrany
2025-06-23 16:10 ` [RFC v5 10/18] gdb/python: allow instantiation of gdb.Compunit from Python Jan Vrany
2025-06-23 16:10 ` [RFC v5 11/18] gdb/python: allow instantiation of gdb.Symtab " Jan Vrany
2025-06-23 16:10 ` [RFC v5 12/18] gdb/python: allow instantiation of gdb.Block " Jan Vrany
2025-06-23 16:10 ` [RFC v5 13/18] gdb/python: allow instantiation of gdb.Symbol " Jan Vrany
2025-06-23 16:10 ` [RFC v5 14/18] gdb/python: add add_symbol () method to gdb.Block Jan Vrany
2025-08-29 14:10 ` Andrew Burgess
2025-08-29 14:14 ` Andrew Burgess
2025-06-23 16:10 ` [RFC v5 15/18] gdb/python: add more attributes to gdb.LinetableEntry objects Jan Vrany
2025-08-29 14:00 ` Andrew Burgess
2025-09-02 11:03 ` Jan Vraný
2025-06-23 16:10 ` Jan Vrany [this message]
2025-06-23 16:10 ` [RFC v5 17/18] gdb/python: allow instantiation of gdb.LineTable objects Jan Vrany
2025-06-23 16:10 ` [RFC v5 18/18] gdb/python: add section in documentation on implementing JIT interface Jan Vrany
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=20250623161013.650814-17-jan.vrany@labware.com \
--to=jan.vrany@labware.com \
--cc=eliz@gnu.org \
--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