Fix latent bug in set_is_exec_point_at
authorTom Tromey <tom@tromey.com>
Sun, 23 Jun 2019 22:07:12 +0000 (16:07 -0600)
committerTom Tromey <tom@tromey.com>
Tue, 25 Jun 2019 13:48:51 +0000 (07:48 -0600)
commitf7952c5774671414d9e0e8d3524c2921daa6f28e
treef6b30b00d226b3936e0b88166fcac16bb97a29f8
parent17568d782d96434537fe9698c5ebcb09f35c20cb
Fix latent bug in set_is_exec_point_at

valgrind pointed out that the TUI was using uninitialized memory in
set_is_exec_point_at.  The bug is a missing check against LOA_ADDRESS,
causing gdb to examine the uninitialized bits of the "addr" field.

gdb/ChangeLog
2019-06-25  Tom Tromey  <tom@tromey.com>

* tui/tui-winsource.c
(tui_source_window_base::set_is_exec_point_at): Add check against
LOA_ADDRESS.
gdb/ChangeLog
gdb/tui/tui-winsource.c