This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/415: Equivalent to bfd_cache_close() for GDB,
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 12 Mar 2002 18:06:20 -0000
- Subject: gdb/415: Equivalent to bfd_cache_close() for GDB,
- Reply-to: ac131313 at redhat dot com
>Number: 415
>Category: gdb
>Synopsis: Equivalent to bfd_cache_close() for GDB,
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Mar 12 10:08:02 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: ac131313@redhat.com
>Release: 2002-03-11
>Organization:
>Environment:
Windows XXX
>Description:
http://sources.redhat.com/ml/gdb-patches/2001-04/msg00205.html
http://sources.redhat.com/ml/gdb/2002-03/msg00100.html
GDB keeps the executable files open so that it is possible to obtain additional information from that file at will (the recently added ``set trust-readonly-sections'' is an example).
The problem is that on Microsoft Windows it isn't possible to override an open file. This messes up things like builds since, unless the executable is closed, the build won't be able to create the new executable while gdb has the old open.
BFD does have an internal function bfd_cache_close(). One way to fix this would be to have BFD publish a function like that (with well defined semantics) so that GDB (and the sim's) could use it.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: