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:
parent
7c96f8c1da
commit
35c61a1dd5
10 changed files with 44 additions and 23 deletions
|
@ -27,7 +27,7 @@ extern PyTypeObject breakpoint_event_object_type
|
|||
/* Create and initialize a BreakpointEvent object. This acquires new
|
||||
references to BREAKPOINT_LIST and FIRST_BP. */
|
||||
|
||||
PyObject *
|
||||
gdbpy_ref<>
|
||||
create_breakpoint_event_object (PyObject *breakpoint_list, PyObject *first_bp)
|
||||
{
|
||||
gdbpy_ref<> breakpoint_event_obj
|
||||
|
@ -45,7 +45,7 @@ create_breakpoint_event_object (PyObject *breakpoint_list, PyObject *first_bp)
|
|||
breakpoint_list) < 0)
|
||||
return NULL;
|
||||
|
||||
return breakpoint_event_obj.release ();
|
||||
return breakpoint_event_obj;
|
||||
}
|
||||
|
||||
GDBPY_NEW_EVENT_TYPE (breakpoint,
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue