On Wed, Nov 25, 2009 at 10:06 AM, Joel Brobecker wrote: >> Should I create a new memory_changed observer and remove >> deprecated_memory_changed_hook instead? > > After reviewing the history of that hook, I think it would be a desired > cleanup to have a memory_changed observer. Cleanup patch attached. Tested on Linux/x86_64 with no regressions. Thanks, -- Paul Pluzhnikov gdb/ChangeLog: 2009-11-25 Paul Pluzhnikov * ada-lang.c (ada_value_assign): Use observer_notify_memory_changed. * valops.c (value_assign): Likewise. * defs.h (deprecated_memory_changed_hook): Remove. * interps.c (clear_interpreter_hooks): Adjust. gdb/doc/ChangeLog: 2009-11-25 Paul Pluzhnikov * observer.texi: New memory_changed observer. gdb/gdbtk/ChangeLog: 2009-11-25 Paul Pluzhnikov * generic/gdbtk-hooks.c (gdbtk_memory_changed): Adjust. (gdbtk_add_hooks): Adjust.