Re: [RFA] win32: bfd_cache_close after kill

[Jerome Guitton <guitton@act-europe.fr>]

Andrew Cagney (cagney@gnu.org):

> >>When the inferior is killed, it is safe the release the different file
> >>>handles that BFD keeps open. It is particularly useful on Win32 (and
> >>>presumably on HP UX) to be able to recompile and restart a new debugging
> >>>session without quitting GDB...
> >
> >
> >New implementation, using bfd_cache_close_all. No regression on i686
> >linux. OK to apply?
> 
> Can it now go in the symbol-table reader that opened the file?

Andrew,

sorry for this late answer, it's hard to find some time these
days... The problem is that I tried to do the change in the
symbol-table reader, but I have several regressions that I need to
investigate before submitting a patch. I am afraid that I won't have
much time to look at them in the coming days, but I will ASAP.

In the meantime, maybe we can integrate the easy part (kill). I think it is
worth it, the documentation already refers to this feature:

"The kill command is also useful if you wish to recompile and relink
your program, since on many systems it is impossible to modify an
executable file while it is running in a process. In this case, when
you next type run, GDB notices that the file has changed, and reads
the symbol table again (while trying to preserve your current
breakpoint settings). "

-- 
Jerome