From 4bde49dc81c5c16189af70b9a144dbb5651994f1 Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Tue, 15 Sep 2020 11:08:56 -0600 Subject: Don't use gdb_py_long_from_longest Change the Python layer to avoid gdb_py_long_from_longest, and remove the defines. gdb/ChangeLog 2020-09-15 Tom Tromey * python/python-internal.h (gdb_py_long_from_longest): Remove defines. * python/py-value.c (valpy_long): Use gdb_py_object_from_longest. * python/py-type.c (convert_field, typy_get_sizeof): Use gdb_py_object_from_longest. * python/py-record-btrace.c (btpy_list_index): Use gdb_py_object_from_longest. --- gdb/python/py-record-btrace.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gdb/python/py-record-btrace.c') diff --git a/gdb/python/py-record-btrace.c b/gdb/python/py-record-btrace.c index 08613a8..84a3d9e 100644 --- a/gdb/python/py-record-btrace.c +++ b/gdb/python/py-record-btrace.c @@ -556,7 +556,7 @@ btpy_list_index (PyObject *self, PyObject *value) if (index < 0) return PyErr_Format (PyExc_ValueError, _("Not in list.")); - return gdb_py_long_from_longest (index); + return gdb_py_object_from_longest (index).release (); } /* Implementation of BtraceList.count (self, value) -> int. */ -- cgit v1.1