Change breakpoint event locations to event_location_up
authorTom Tromey <tom@tromey.com>
Mon, 10 Apr 2017 21:41:25 +0000 (15:41 -0600)
committerTom Tromey <tom@tromey.com>
Wed, 12 Apr 2017 17:16:19 +0000 (11:16 -0600)
commitd28cd78ad820e3a40ac5064b6a30f3a12ce70bf0
treeb89ce13dcab2b791cde8073a77fddc53dd06083f
parent711799d513206f6d8fc3dbfa81dcdecdb2ce6ece
Change breakpoint event locations to event_location_up

This is a follow-up to an earlier patch.  It changes breakpoint's
location and location_range_end members to be of type
event_location_up, then fixes up the users.

gdb/ChangeLog
2017-04-12  Tom Tromey  <tom@tromey.com>

* remote.c (remote_download_tracepoint): Update.
* python/py-breakpoint.c (bppy_get_location): Update.
* guile/scm-breakpoint.c (bpscm_print_breakpoint_smob)
(gdbscm_breakpoint_location): Update.
* elfread.c (elf_gnu_ifunc_resolver_return_stop): Update.
* breakpoint.h (struct breakpoint) <location, location_range_end>:
Change type to event_location_up.
* breakpoint.c (create_overlay_event_breakpoint)
(create_longjmp_master_breakpoint)
(create_std_terminate_master_breakpoint)
(create_exception_master_breakpoint)
(breakpoint_event_location_empty_p, print_breakpoint_location)
(print_one_breakpoint_location, create_thread_event_breakpoint)
(init_breakpoint_sal, create_breakpoint)
(print_recreate_ranged_breakpoint, break_range_command)
(init_ada_exception_breakpoint, say_where): Update.
(base_breakpoint_dtor): Don't call delete_event_location.
(bkpt_print_recreate, tracepoint_print_recreate)
(dprintf_print_recreate, update_static_tracepoint)
(breakpoint_re_set_default): Update.
gdb/ChangeLog
gdb/breakpoint.c
gdb/breakpoint.h
gdb/elfread.c
gdb/guile/scm-breakpoint.c
gdb/python/py-breakpoint.c
gdb/remote.c