mirror of
https://github.com/espressif/binutils-gdb.git
synced 2025-05-30 07:49:07 +08:00
Small event ownership clean up in Python layer
It seems cleaner to me for functions like create_thread_event_object, which pass object ownership to their callers, to directly return a gdb_ref<>. This way the ownership transfer is part of the API. This patch makes this change. ChangeLog 2017-09-11 Tom Tromey <tom@tromey.com> * python/py-threadevent.c (create_thread_event_object): Return gdbpy_ref. * python/py-stopevent.h (create_stop_event_object) (create_breakpoint_event_object, create_signal_event_object): Update. * python/py-stopevent.c (create_stop_event_object): Return gdbpy_ref. (emit_stop_event): Update. * python/py-signalevent.c (create_signal_event_object): Return gdbpy_ref. * python/py-infevents.c (create_inferior_call_event_object): Update. * python/py-event.h (create_event_object) (create_thread_event_object): Update. * python/py-event.c (create_event_object): Return gdbpy_ref. * python/py-continueevent.c: Return gdbpy_ref. * python/py-bpevent.c (create_breakpoint_event_object): Return gdbpy_ref.
This commit is contained in:
@ -47,7 +47,7 @@ get_event_thread (void)
|
||||
return thread;
|
||||
}
|
||||
|
||||
PyObject *
|
||||
gdbpy_ref<>
|
||||
create_thread_event_object (PyTypeObject *py_type, PyObject *thread)
|
||||
{
|
||||
gdbpy_ref<> thread_event_obj (create_event_object (py_type));
|
||||
@ -66,7 +66,7 @@ create_thread_event_object (PyTypeObject *py_type, PyObject *thread)
|
||||
thread) < 0)
|
||||
return NULL;
|
||||
|
||||
return thread_event_obj.release ();
|
||||
return thread_event_obj;
|
||||
}
|
||||
|
||||
GDBPY_NEW_EVENT_TYPE (thread,
|
||||
|
Reference in New Issue
Block a user