Don't use PyLong_FromLongLong
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:
parent
062534d44f
commit
4ab1029c56
3 changed files with 9 additions and 2 deletions
|
@ -1,3 +1,10 @@
|
||||||
|
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.
|
||||||
|
|
||||||
2020-09-15 Tom Tromey <tromey@adacore.com>
|
2020-09-15 Tom Tromey <tromey@adacore.com>
|
||||||
|
|
||||||
* python/python.c (gdbpy_parameter_value): Use
|
* python/python.c (gdbpy_parameter_value): Use
|
||||||
|
|
|
@ -30,7 +30,7 @@ create_exited_event_object (const LONGEST *exit_code, struct inferior *inf)
|
||||||
|
|
||||||
if (exit_code)
|
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)
|
if (exit_code_obj == NULL)
|
||||||
return NULL;
|
return NULL;
|
||||||
|
|
|
@ -76,7 +76,7 @@ create_register_changed_event_object (struct frame_info *frame,
|
||||||
if (evpy_add_attribute (event.get (), "frame", frame_obj.get ()) < 0)
|
if (evpy_add_attribute (event.get (), "frame", frame_obj.get ()) < 0)
|
||||||
return NULL;
|
return NULL;
|
||||||
|
|
||||||
gdbpy_ref<> regnum_obj (PyLong_FromLongLong (regnum));
|
gdbpy_ref<> regnum_obj = gdb_py_object_from_longest (regnum);
|
||||||
if (regnum_obj == NULL)
|
if (regnum_obj == NULL)
|
||||||
return NULL;
|
return NULL;
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue