Don't use gdb_py_long_from_ulongest
Remove the gdb_py_long_from_ulongest defines and change the Python layer to prefer gdb_py_object_from_ulongest. While writing this I noticed that the error handling in archpy_disassemble was incorrect -- it could call PyDict_SetItemString with a NULL value. This patch also fixes this bug. gdb/ChangeLog 2020-09-15 Tom Tromey <tromey@adacore.com> * python/python-internal.h (gdb_py_long_from_ulongest): Remove defines. * python/py-value.c (valpy_long): Use gdb_py_object_from_ulongest. * python/py-symtab.c (salpy_get_pc): Use gdb_py_object_from_ulongest. (salpy_get_last): Likewise. * python/py-record-btrace.c (recpy_bt_insn_pc): Use gdb_py_object_from_ulongest. * python/py-lazy-string.c (stpy_get_address): Use gdb_py_object_from_ulongest. * python/py-frame.c (frapy_pc): Use gdb_py_object_from_ulongest. * python/py-arch.c (archpy_disassemble): Use gdb_py_object_from_ulongest and gdb_py_object_from_longest. Fix error handling.
This commit is contained in:
parent
4bde49dc81
commit
d1cab9876d
8 changed files with 41 additions and 16 deletions
|
@ -126,7 +126,6 @@
|
|||
#define GDB_PY_LLU_ARG "K"
|
||||
typedef PY_LONG_LONG gdb_py_longest;
|
||||
typedef unsigned PY_LONG_LONG gdb_py_ulongest;
|
||||
#define gdb_py_long_from_ulongest PyLong_FromUnsignedLongLong
|
||||
#define gdb_py_long_as_ulongest PyLong_AsUnsignedLongLong
|
||||
|
||||
#else /* HAVE_LONG_LONG */
|
||||
|
@ -135,7 +134,6 @@ typedef unsigned PY_LONG_LONG gdb_py_ulongest;
|
|||
#define GDB_PY_LLU_ARG "K"
|
||||
typedef long gdb_py_longest;
|
||||
typedef unsigned long gdb_py_ulongest;
|
||||
#define gdb_py_long_from_ulongest PyLong_FromUnsignedLong
|
||||
#define gdb_py_long_as_ulongest PyLong_AsUnsignedLong
|
||||
|
||||
#endif /* HAVE_LONG_LONG */
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue