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 <tromey@adacore.com> * 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.
This commit is contained in:
parent
3743107465
commit
4bde49dc81
5 changed files with 15 additions and 9 deletions
|
@ -1733,7 +1733,7 @@ valpy_long (PyObject *self)
|
|||
if (type->is_unsigned ())
|
||||
return gdb_py_long_from_ulongest (l);
|
||||
else
|
||||
return gdb_py_long_from_longest (l);
|
||||
return gdb_py_object_from_longest (l).release ();
|
||||
}
|
||||
|
||||
/* Implements conversion to float. */
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue