From 02aadca4fbeadbab6584222ca78dbc24c79f5229 Mon Sep 17 00:00:00 2001 From: Andrew Burgess Date: Thu, 16 Feb 2023 19:07:12 +0000 Subject: [PATCH] gdb: remove an out of date comment about disp_del_at_next_stop Delete an out of date comment about disp_del_at_next_stop, the comment says: /* NOTE drow/2003-09-08: This state only exists for removing watchpoints. It's not clear that it's necessary... */ I'm sure this was true when the comment was added, but today the disp_del_at_next_stop state is not just used for deleting watchpoints, which leaves us with "It's not clear that it's necessary...", which doesn't really help at all. And then this comment is located on one random place where disp_del_at_next_stop is used, rather than at its definition site. Lets just delete the comment. No user visible changes after this commit. Reviewed-By: Pedro Alves --- gdb/breakpoint.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c index ebf9d8f1349..7d11f7199fe 100644 --- a/gdb/breakpoint.c +++ b/gdb/breakpoint.c @@ -2938,8 +2938,6 @@ insert_bp_location (struct bp_location *bl, } else if (bl->loc_type == bp_loc_hardware_watchpoint - /* NOTE drow/2003-09-08: This state only exists for removing - watchpoints. It's not clear that it's necessary... */ && bl->owner->disposition != disp_del_at_next_stop) { int val; -- 2.30.2