Re: Static tracepoints support

Pedro Alves
2010-07-01T14:00:38Z

On Monday 28 June 2010 13:26:38, Pedro Alves wrote:
> > > +with that name. With no LOCATION, uses current execution address of \n\
> > > +selected stack frame.\n\
> >
> > "of the selected stack frame"
>
> Fixed. Needs fixing in BREAK_ARGS_HELP; it's showing up in the help
> strings of all breakpoint commands.
>

Here's the fix for all other breakpoint commands, but I do
note some sort of pattern here: it appears that "the" was
avoided on purpose in all the sentences as can be seen in
the contenxt of the patch. Would you like to review
the whole help string, or is this correct?

--
Pedro Alves

2010-07-01 Pedro Alves <pedro@codesourcery.com>

* breakpoint.c (BREAK_ARGS_HELP): Add missing `the'.

---
gdb/breakpoint.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Index: src/gdb/breakpoint.c
===================================================================
--- src.orig/gdb/breakpoint.c 2010-07-01 14:51:37.000000000 +0100
+++ src/gdb/breakpoint.c 2010-07-01 14:52:54.000000000 +0100
@@ -11496,8 +11496,8 @@ LOCATION may be a line number, function
If a line number is specified, break at start of code for that line.\n\
If a function is specified, break at start of code for that function.\n\
If an address is specified, break at that exact address.\n\
-With no LOCATION, uses current execution address of selected stack frame.\n\
-This is useful for breaking on return to a stack frame.\n\
+With no LOCATION, uses current execution address of the selected\n\
+stack frame. This is useful for breaking on return to a stack frame.\n\
\n\
THREADNUM is the number from \"info threads\".\n\
CONDITION is a boolean expression.\n\