Fix use-after-move bug in add_thread_object
commit 05b08ac160
("Reduce manual reference counting in
py-inferior.c") introduced a use-after-move bug in add_thread_object,
causing a test suite failure. This patch fixes the bug.
Tested on x86-64 Fedora 29.
gdb/ChangeLog
2019-07-11 Tom Tromey <tromey@adacore.com>
* python/py-inferior.c (add_thread_object): Don't use thread_obj
after it has been moved.
This commit is contained in:
parent
00db953196
commit
72ee03ff58
2 changed files with 6 additions and 1 deletions
|
@ -344,7 +344,7 @@ add_thread_object (struct thread_info *tp)
|
|||
return;
|
||||
|
||||
gdbpy_ref<> event = create_thread_event_object (&new_thread_event_object_type,
|
||||
(PyObject *) thread_obj.get ());
|
||||
(PyObject *) inf_obj);
|
||||
if (event == NULL
|
||||
|| evpy_emit_event (event.get (), gdb_py_events.new_thread) < 0)
|
||||
gdbpy_print_stack ();
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue