[OB] fix comment in breakponit.c

[OB] fix comment in breakponit.c

[Michael Snyder]

[-- Attachment #1: Type: text/plain, Size: 49 bytes --]

Probably busted by a global search and replace?


[-- Attachment #2: already.txt --]
[-- Type: text/plain, Size: 778 bytes --]

2009-10-31  Michael Snyder  <msnyder@vmware.com>

	* breakpoint.c (bpstat_stop_status): Fix broken comment.

Index: breakpoint.c
===================================================================
RCS file: /cvs/src/src/gdb/breakpoint.c,v
retrieving revision 1.422
diff -u -p -r1.422 breakpoint.c
--- breakpoint.c	31 Oct 2009 06:00:11 -0000	1.422
+++ breakpoint.c	31 Oct 2009 18:29:59 -0000
@@ -3457,8 +3457,7 @@ bpstat_stop_status (struct address_space
        The watchpoint_check function will work on entire expression,
        not the individual locations.  For read watchopints, the
        watchpoints_triggered function have checked all locations
-       alrea
-     */
+       already.  */
     if (b->type == bp_hardware_watchpoint && bl != b->loc)
       continue;
 

Re: [OB] fix comment in breakponit.c

[Pedro Alves]

On Saturday 31 October 2009 18:23:14, Michael Snyder Wrote:
> @@ -3457,8 +3457,7 @@ bpstat_stop_status (struct address_space
>         The watchpoint_check function will work on entire expression,
>         not the individual locations.  For read watchopints, the
>         watchpoints_triggered function have checked all locations
> -       alrea
> -     */
> +       already.  */

Watch-O-Pints?

-- 
Pedro Alves

Re: [OB] fix comment in breakponit.c

[Michael Snyder]

Pedro Alves wrote:
> On Saturday 31 October 2009 18:23:14, Michael Snyder Wrote:
>> @@ -3457,8 +3457,7 @@ bpstat_stop_status (struct address_space
>>         The watchpoint_check function will work on entire expression,
>>         not the individual locations.  For read watchopints, the
>>         watchpoints_triggered function have checked all locations
>> -       alrea
>> -     */
>> +       already.  */
> 
> Watch-O-Pints?

Heh.  I didn't even do that one.  Looks like one I would do, though.
;-)

We'll have to hoist a watch-o-pint at the next gcc summit.