gdb/python: Use copy-initialization more when possible
gdb/ChangeLog: 2018-08-24 Pedro Alves <palves@redhat.com> * python/py-bpevent.c (create_breakpoint_event_object): Use copy-initialization. * python/py-continueevent.c (emit_continue_event): Use copy-initialization. * python/py-exitedevent.c (create_exited_event_object): Return a gdbpy_ref<>. (emit_exited_event): Use copy-initialization. * python/py-inferior.c (python_new_inferior) (python_inferior_deleted, add_thread_object): Use copy-initialization. * python/py-infevents.c (create_inferior_call_event_object) (create_register_changed_event_object) (create_memory_changed_event_object): Return a gdbpy_ref<>. (emit_inferior_call_event, emit_memory_changed_event) (emit_register_changed_event): Use copy-initialization. * python/py-newobjfileevent.c (create_new_objfile_event_object): Return a gdbpy_ref<>. (emit_new_objfile_event): Use copy-initialization. (create_clear_objfiles_event_object): Return a gdbpy_ref<>. (emit_clear_objfiles_event): Use copy-initialization. * python/py-signalevent.c (create_signal_event_object): Use copy-initialization. * python/py-threadevent.c (create_thread_event_object): Use copy-initialization.
This commit is contained in:
parent
da3c873831
commit
d98fc15be2
9 changed files with 61 additions and 39 deletions
|
@ -23,14 +23,13 @@
|
|||
gdbpy_ref<>
|
||||
create_signal_event_object (enum gdb_signal stop_signal)
|
||||
{
|
||||
const char *signal_name;
|
||||
gdbpy_ref<> signal_event_obj
|
||||
(create_stop_event_object (&signal_event_object_type));
|
||||
= create_stop_event_object (&signal_event_object_type);
|
||||
|
||||
if (signal_event_obj == NULL)
|
||||
return NULL;
|
||||
|
||||
signal_name = gdb_signal_to_name (stop_signal);
|
||||
const char *signal_name = gdb_signal_to_name (stop_signal);
|
||||
|
||||
gdbpy_ref<> signal_name_obj (PyString_FromString (signal_name));
|
||||
if (signal_name_obj == NULL)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue