gdb: remove final user of the executable_changed observer
This commit continues with the task started in the previous commit,
and is similar in many ways.
The goal of the next couple of commits is to expose the
executable_changed observable in the Python API as an event. Before I
do this I would like to remove the additional call to the
executable_changed observable which can be found in the reread_symbols
function in the symfile.c file, as I don't believe that this use
actually corresponds to a change in the current executable.
The previous commit removed one user of the executable_changed
observable and replaced it with a new_obfile observer instead, and
this commit does the same thing.
In auxv.c we use the executable_changed observable to call
invalidate_auxv_cache, which then calls:
invalidate_auxv_cache_inf (current_inferior ());
The auxv cache is already (additionally) cleared when an inferior
exits and when an inferior appears.
As with the previous commit, I think we can safely replace the use of
the executable_changed observable with a use of the new_obfile
observable. All the tests still pass, and with some locally placed
printf calls, I think that the cache is still being cleared in all the
cases that should matter.
Approved-By: Tom Tromey <tom@tromey.com>