diff options
author | Daniel Jacobowitz <dan@debian.org> | 2008-03-14 18:39:41 +0000 |
---|---|---|
committer | Daniel Jacobowitz <dan@debian.org> | 2008-03-14 18:39:41 +0000 |
commit | 210f7fd5435b84edb7c19a116e7c5e89777ebbb1 (patch) | |
tree | ea5718da1676af432608f67ee24d32290ac6258d /bfd/cache.c | |
parent | 77b97e196ec74e448bcc5279913d902fdaba690b (diff) | |
download | binutils-redhat-210f7fd5435b84edb7c19a116e7c5e89777ebbb1.tar.gz |
* cache.c (close_one): Remove mtime hack.
* corefile.c (reopen_exec_file): Use exec_bfd_mtime.
* exec.c (exec_bfd_mtime): Define.
(exec_close): Clear it.
(exec_file_attach): Set it.
* gdbcore.h (exec_bfd_mtime): Declare.
* source.c (find_source_lines): Do not use bfd_get_mtime.
Diffstat (limited to 'bfd/cache.c')
-rw-r--r-- | bfd/cache.c | 16 |
1 files changed, 0 insertions, 16 deletions
diff --git a/bfd/cache.c b/bfd/cache.c index 064cebeb3c..eb6120dfbe 100644 --- a/bfd/cache.c +++ b/bfd/cache.c @@ -166,22 +166,6 @@ close_one (void) kill->where = real_ftell ((FILE *) kill->iostream); - /* Save the file st_mtime. This is a hack so that gdb can detect when - an executable has been deleted and recreated. The only thing that - makes this reasonable is that st_mtime doesn't change when a file - is unlinked, so saving st_mtime makes BFD's file cache operation - a little more transparent for this particular usage pattern. If we - hadn't closed the file then we would not have lost the original - contents, st_mtime etc. Of course, if something is writing to an - existing file, then this is the wrong thing to do. - FIXME: gdb should save these times itself on first opening a file, - and this hack be removed. */ - if (kill->direction == no_direction || kill->direction == read_direction) - { - bfd_get_mtime (kill); - kill->mtime_set = TRUE; - } - return bfd_cache_delete (kill); } |