clarify "help break" output a bit (Re: Static tracepoints support)

[Pedro Alves <pedro@codesourcery.com>]

On Wednesday 30 June 2010 19:16:09, Eli Zaretskii wrote:
> > > But only if the conditionals are different.
> > > 
> > > Anyway, it confused me, so perhaps it's a good idea to clarify.
> > 
> > Okay, I agree, though I'd prefer to do that as a follow up, where I
> > change both the break- and tracepoint command's help output at once.
> > Is that okay with you?
> 
> Yes.

Thanks.  Here's a patch.  Okay?

-- 
Pedro Alves

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

	* breakpoint.c (BREAK_ARGS_HELP, _initialize_breakpoint): Clarify
	usefulness suggestion of multiple breakpoints at same location.

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

Index: src/gdb/breakpoint.c
===================================================================
--- src.orig/gdb/breakpoint.c	2010-07-01 15:16:13.000000000 +0100
+++ src/gdb/breakpoint.c	2010-07-01 15:17:29.000000000 +0100
@@ -11502,7 +11502,8 @@ stack frame.  This is useful for breakin
 THREADNUM is the number from \"info threads\".\n\
 CONDITION is a boolean expression.\n\
 \n\
-Multiple breakpoints at one place are permitted, and useful if conditional.\n\
+Multiple breakpoints at one place are permitted, and useful if their\n\
+conditions are different.\n\
 \n\
 Do \"help breakpoints\" for info on other commands dealing with breakpoints."
 
@@ -11956,7 +11957,8 @@ by printing the $_sdata variable like an
 \n\
 CONDITION is a boolean expression.\n\
 \n\
-Multiple tracepoints at one place are permitted, and useful if conditional.\n\
+Multiple tracepoints at one place are permitted, and useful if their\n\
+conditions are different.\n\
 \n\
 Do \"help breakpoints\" for info on other commands dealing with breakpoints.\n\
 Do \"help tracepoints\" for info on other tracepoint commands."));