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.
This commit is contained in:
parent
a96e36da2f
commit
39a67dc4f7
2 changed files with 6 additions and 1 deletions
|
@ -1,3 +1,8 @@
|
|||
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
|
||||
|
|
|
@ -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);
|
||||
|
|
Loading…
Reference in a new issue