Don't use gdb_py_long_from_ulongest

[deliverable/binutils-gdb.git] / gdb / ChangeLog

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 6df6633b00ab0d6a3f171d965e2648f9be69a47b..504a916314f6adbf060c905dca8f298379bc61cd 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,21 @@
+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.
+
 2020-09-15  Tom Tromey  <tromey@adacore.com>
 
        * python/python-internal.h (gdb_py_long_from_longest): Remove