[PATCH 0/3] bfd cache: tighten match criteria and debug commands.

[Andrew Burgess <andrew dot burgess at embecosm dot com>]

I ran into this problem:
 https://www.sourceware.org/ml/gdb/2013-11/msg00080.html
that thread contained some good ideas, but as far as I can see didn't
result in any changes being committed.

In patch #1 I've made the file size an additional metric used to
determine if the on disc file has changed.  As Luis points out this
will not solve the problem in all cases, but it should make things
better than they are at the moment.

The consensus in the thread was, I think, that using inode information
might be the best solution.  I did look at this, but was not sure the
right place to hook this in; I guess I'd need to add some new bfd
functions.

Given that any solution using inodes would probably be on top of the
existing match criteria, and that obtaining the file size is pretty
cheep, I figured there's little harm is having this in place now, and
adding an inode based criteria later, if wanted.

Patches #2 and #3 are both maintainer related; #2 provides a mechanism
to disable the bfd cache, and #3 adds debug logging to the cache
mechanism.

Thanks,
Andrew

Andrew Burgess (3):
  gdb: Use bfd size as another cache identification criteria.
  gdb: New maintenance command to disable bfd sharing.
  gdb: Add debug tracing for bfd cache activity.

 gdb/ChangeLog | 25 +++++++++++++++++
 gdb/NEWS      |  8 ++++++
 gdb/gdb_bfd.c | 88 +++++++++++++++++++++++++++++++++++++++++++++++++++++++----
 3 files changed, 115 insertions(+), 6 deletions(-)

-- 
2.2.2