From 63283d4a2983eaefd5d0860ddffcf946f0fe92db Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Sun, 23 Apr 2017 11:07:26 -0600 Subject: Remove EXT_LANG_BT_COMPLETED While looking at the frame filter code, I noticed that EXT_LANG_BT_COMPLETED is not really needed. Semantically there is no difference between the "completed" and "ok" results. So, this patch removes this constant. gdb/ChangeLog 2018-03-26 Tom Tromey * python/py-framefilter.c (py_print_frame): Return EXT_LANG_BT_OK. (gdbpy_apply_frame_filter): Update comment. * extension.h (enum ext_lang_bt_status) : Remove. : Change value. --- gdb/extension.h | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) (limited to 'gdb/extension.h') diff --git a/gdb/extension.h b/gdb/extension.h index a972928..c675ae2 100644 --- a/gdb/extension.h +++ b/gdb/extension.h @@ -76,13 +76,9 @@ enum ext_lang_bt_status succeeded. */ EXT_LANG_BT_OK = 1, - /* Return when the frame filter process is complete, and all - operations have succeeded. */ - EXT_LANG_BT_COMPLETED = 2, - /* Return when the frame filter process is complete, but there were no filter registered and enabled to process. */ - EXT_LANG_BT_NO_FILTERS = 3 + EXT_LANG_BT_NO_FILTERS = 2 }; /* Flags to pass to apply_extlang_frame_filter. */ -- cgit v1.1