diff mbox series

[1/8] gdb: remove an out of date comment about disp_del_at_next_stop

Message ID b7767c19f7e14299d67cdcbaf706179218a740bc.1676901929.git.aburgess@redhat.com
State Committed
Commit 02aadca4fbeadbab6584222ca78dbc24c79f5229
Headers
Series Fix missing MI =breakpoint-deleted notifications |

Commit Message

Andrew Burgess Feb. 20, 2023, 2:13 p.m. UTC 
  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.
---
 gdb/breakpoint.c | 2 --
 1 file changed, 2 deletions(-)
diff mbox series

Patch

diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index 0db3adaf916..902119c7d2c 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;