[binutils-gdb] Enable/update legacy linespecs in MI.

[Keith Seitz <kseitz at sourceware dot org>]

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=39a67dc4f7d032c78f031e2d101b9552f1a6b57f

commit 39a67dc4f7d032c78f031e2d101b9552f1a6b57f
Author: Keith Seitz <keiths@redhat.com>
Date:   Tue Feb 9 10:02:54 2016 -0800

    Enable/update legacy linespecs in MI.
    
    MI is currently using string_to_event_location to enable the use of legacy
    linespecs, but using this function (until this patchset) had the (as yet
    unnoticed) side effect of allowing both MI and CLI representation for
    explicit locations.
    
    This patch simply changes MI to use the same legacy linespec functions
    that the python and guile interpreters use.  This eliminates the CLI syntax
    for explicit locations (in MI).
    
    gdb/ChangeLog
    
    	* mi/mi-cmd-break.c (mi_cmd_break_insert_1): Use
    	string_to_event_location_basic instead of string_to_event_location.

Diff:
---
 gdb/ChangeLog         | 5 +++++
 gdb/mi/mi-cmd-break.c | 2 +-
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index f7591ff..04daf07 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,10 @@
 2016-02-09  Keith Seitz  <keiths@redhat.com>
 
+	* mi/mi-cmd-break.c (mi_cmd_break_insert_1): Use
+	string_to_event_location_basic instead of string_to_event_location.
+
+2016-02-09  Keith Seitz  <keiths@redhat.com>
+
 	* guile/scm-breakpoint.c (gdbscm_register_breakpoint_x): Skip
 	leading whitespace and use string_to_event_location_basic instead
 	of new_linespec_location.
diff --git a/gdb/mi/mi-cmd-break.c b/gdb/mi/mi-cmd-break.c
index ef3ce29..3d40629 100644
--- a/gdb/mi/mi-cmd-break.c
+++ b/gdb/mi/mi-cmd-break.c
@@ -341,7 +341,7 @@ mi_cmd_break_insert_1 (int dprintf, char *command, char **argv, int argc)
     }
   else
     {
-      location = string_to_event_location (&address, current_language);
+      location = string_to_event_location_basic (&address, current_language);
       if (*address)
 	{
 	  delete_event_location (location);