[PATCH 0/6] Remove some Python safety FIXME comments

[Tom Tromey <tom@tromey.com>]

I realized somewhat belatedly that instead of adding FIXME comments
for Python safety issues, I could write wrapper functions that enforce
the safety approach; and then the goal would shift to eventually
merging the wrappers with the function they wrap.

This series does this.  Tested on x86-64 Fedora 40.

Signed-off-by: Tom Tromey <tom@tromey.com>
---
Tom Tromey (6):
      Add safe_target_to_connection_object
      Add safety wrappers for from_{longest,ulongest}
      Add gdbpy_safe_invalid_object_repr
      Some symbol-related Python safety fixes
      Safe wrappers for some string conversions
      Some frame-related Python safety fixes

 gdb/python/py-arch.c         | 18 ++---------
 gdb/python/py-connection.c   | 22 ++++++++------
 gdb/python/py-frame.c        | 71 +++++++++++++++-----------------------------
 gdb/python/py-inferior.c     |  2 +-
 gdb/python/py-ref.h          |  7 +++++
 gdb/python/py-safety.h       | 21 +++++++++++++
 gdb/python/py-symbol.c       | 64 +++++++++++----------------------------
 gdb/python/py-tui.c          |  7 +----
 gdb/python/py-utils.c        | 20 +++++++++++++
 gdb/python/py-wrappers.h     | 30 +++++++++++++++++++
 gdb/python/python-internal.h | 21 +++++++++----
 11 files changed, 152 insertions(+), 131 deletions(-)
---
base-commit: 31249660c695a9169ca97590a2c325585740c101
change-id: 20261023-python-safety-fixmes-dfcd48d107b6

Best regards,
-- 
Tom Tromey <tom@tromey.com>