FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Don't use PyLong_FromLongLong

Browse source 
This changes gdb to avoid PyLong_FromLongLong, preferring to use
gdb_py_object_from_longest instead.

gdb/ChangeLog
2020-09-15  Tom Tromey  <tromey@adacore.com>

	* python/py-infevents.c (create_register_changed_event_object):
	Use gdb_py_object_from_longest.
	* python/py-exitedevent.c (create_exited_event_object): Use
	gdb_py_object_from_longest.
This commit is contained in:
Tom Tromey 2020-09-15 11:08:56 -06:00
parent 062534d44f
commit 4ab1029c56
3 changed files with 9 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
gdb/python/py-exitedevent.c
View file

@ -30,7 +30,7 @@ create_exited_event_object (const LONGEST *exit_code, struct inferior *inf)
if (exit_code)
{
gdbpy_ref<> exit_code_obj (PyLong_FromLongLong (*exit_code));
gdbpy_ref<> exit_code_obj = gdb_py_object_from_longest (*exit_code);
if (exit_code_obj == NULL)
return NULL;

2
gdb/python/py-infevents.c
View file

@ -76,7 +76,7 @@ create_register_changed_event_object (struct frame_info *frame,
if (evpy_add_attribute (event.get (), "frame", frame_obj.get ()) < 0)
return NULL;
gdbpy_ref<> regnum_obj (PyLong_FromLongLong (regnum));
gdbpy_ref<> regnum_obj = gdb_py_object_from_longest (regnum);
if (regnum_obj == NULL)
return NULL;