From 7c03e522d4e059a7c59533e4b01771a7cc4bb68e Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Tue, 11 Jun 2024 14:10:08 -0600 Subject: Return gdbpy_ref<> from gdbpy_call_method This changes gdbpy_call_method to return a gdbpy_ref<>. This is slightly safer because it makes it simpler to correctly handle reference counts. Reviewed-By: Tom de Vries --- gdb/python/py-finishbreakpoint.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gdb/python/py-finishbreakpoint.c') diff --git a/gdb/python/py-finishbreakpoint.c b/gdb/python/py-finishbreakpoint.c index 1b620e6..78030be 100644 --- a/gdb/python/py-finishbreakpoint.c +++ b/gdb/python/py-finishbreakpoint.c @@ -344,7 +344,7 @@ bpfinishpy_out_of_scope (struct finish_breakpoint_object *bpfinish_obj) if (bpfinish_obj->py_bp.bp->enable_state == bp_enabled && PyObject_HasAttrString (py_obj, outofscope_func)) { - gdbpy_ref<> meth_result (gdbpy_call_method (py_obj, outofscope_func)); + gdbpy_ref<> meth_result = gdbpy_call_method (py_obj, outofscope_func); if (meth_result == NULL) gdbpy_print_stack (); } -- cgit v1.1