From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
To: Andrew Burgess <aburgess@redhat.com>, <binutils@sourceware.org>
Subject: Re: [PATCH] bfd: add new bfd_cache_size() function
Date: Fri, 6 Oct 2023 23:09:42 +0200 [thread overview]
Message-ID: <3d574beb-7a1d-ac3d-bebd-d4e85ee185c8@foss.st.com> (raw)
In-Reply-To: <bab49cf8bb040a1c8f43a741e076ebb97135e06a.1696608163.git.aburgess@redhat.com>
On 2023-10-06 18:03, Andrew Burgess via Binutils wrote:
> In GDB we have a problem with the BFD cache.
>
> As GDB runs for a potentially extended period of time, if the BFD
> cache holds a file descriptor for an open on-disk file, this can, on
> some targets (e.g. Win32) prevent the OS writing to the file.
>
> This might, for example, prevent a user from recompiling their
> executable as GDB is (via the BFD cache) holding an open reference to
> that file.
>
> Another problem, relates to bfd_stat, for BFDs that are using the BFD
> cache (i.e. they call cache_bstat to implement bfd_stat). The
> cache_bstat function finds the BFD in the cache, opening the file if
> needed, and then uses fstat on the open file descriptor.
>
> What this means is that, if the on-disk file changes, but the cache
> was holding an open reference to the file, the bfd_stat will return
> the 'struct stat' for the old file, not the new file.
>
> Now, for this second problem, we might be tempted to make use of an
> actual stat call, instead of calling bfd_stat, however, this isn't
> ideal as we have some BFDs that use a custom iovec, and implement the
> various functions over GDB's remote protocol. By using bfd_stat we
> can have a single call that should work for both local files, and for
> remote files.
>
> To solve both of these problems GDB has calls to bfd_cache_close_all
> sprinkled around its code base. And in theory this should work fine.
>
> However, I recently ran into a case where we had missed a
> bfd_cache_close_all call, and as a result some BFDs were held open.
> This caused a bfd_stat call to return an unexpected result (old file
> vs new file).
>
> What I'd like is some way within GDB that I can do:
>
> gdb_assert ( /* Nothing is held open in the cache. */ );
>
> As this would allow GDB to quickly identify when we've missed some
> bfd_cache_close_all calls.
>
> And so, to support this, I would like to add a new bfd_cache_size
> function. This function returns an integer, which is the number of
> open files in the cache. I can then start adding:
>
> gdb_assert (bfd_cache_size() == 0);
>
> to GDB in some strategic spots, and start fixing all of the missing
> bfd_cache_close_all calls that crop up as a result.
I think this sounds reasonable, but I'm not a maintainer so you need
someone else to approve this.
next prev parent reply other threads:[~2023-10-06 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 16:03 Andrew Burgess
2023-10-06 21:09 ` Torbjorn SVENSSON [this message]
2023-10-09 14:01 ` Nick Clifton
2023-10-11 13:50 ` Andrew Burgess
2023-10-12 12:32 ` Nick Clifton
2023-10-12 13:00 ` Andrew Burgess
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d574beb-7a1d-ac3d-bebd-d4e85ee185c8@foss.st.com \
--to=torbjorn.svensson@foss.st.com \
--cc=aburgess@redhat.com \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).