* breakpoint.c (break_range_command): Fix typo in comment.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 4da68a0fcefcc113b9a1a5ab026bc25e5aa9a710..1029fb275c840875d065e2d84613ba91b982f978 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2011-03-31  Thiago Jung Bauermann  <bauerman@br.ibm.com>
+
+       * breakpoint.c (break_range_command): Fix typo in comment.
+
 2011-03-31  Thiago Jung Bauermann  <bauerman@br.ibm.com>
            Sergio Durigan Junior  <sergiodj@linux.vnet.ibm.com>
 

diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index 863198fa532f35e54251004a8822e23b4b573def..3b1367bb4659e5bae9a85161e3fcd7a30f560eeb 100644 (file)
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -8594,7 +8594,7 @@ break_range_command (char *arg, int from_tty)
   init_linespec_result (&canonical_end);
   arg_start = arg;
 
-  /* We call decode_line_n1 directly here instead of using
+  /* We call decode_line_1 directly here instead of using
      parse_breakpoint_sals because we need to specify the start location's
      symtab and line as the default symtab and line for the end of the
      range.  This makes it possible to have ranges like "foo.c:27, +14",