Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: one-liner patches to sim/common
Date: Sat, 21 Apr 2001 15:40:00 -0000	[thread overview]
Message-ID: <3AE20C2B.DC87C56D@cygnus.com> (raw)
In-Reply-To: <20010419170124.D29382@redhat.com>

"Frank Ch. Eigler" wrote:
> 
> Hi -
> 
> I just committed a one-liner pair of patches, as suggested by
> Andrew Cagney, to get around some annoying problems related
> to the sim/gdb hanging on to executable file handles
> unnecessarily.

Er, that's not correct.

I pointed out that Insight had *hacked* around a problem with locked
files on WindowsSOMETHING by closing the BFD using the *INTERNAL*
function bfd_cache_close().

Neither GDB, sim/common or Insight should be calling functions that are
internal to BFD.  If you think the function is useful then please get
BFD to publish its interface:

cc1: warnings being treated as errors
/home/scratch/MI/src/sim/d10v/../common/sim-load.c: In function
`sim_load_file':
/home/scratch/MI/src/sim/d10v/../common/sim-load.c:169: warning:
implicit declaration of function `bfd_cache_close'
*** Error code 1

	Andrew


> 2001-04-19  Frank Ch. Eigler  <fche@redhat.com>
> 
>         * sim-utils.c (sim_analyze_program): Call bfd_cache_close after
>         we're finished with its immediate use.
>         * sim-load.c (sim_load_file): Ditto.
> 
> Index: sim-load.c
> ===================================================================
> RCS file: /cvs/cvsfiles/devo/sim/common/sim-load.c,v
> retrieving revision 1.9
> diff -u -r1.9 sim-load.c
> --- sim-load.c  2000/03/02 09:10:40     1.9
> +++ sim-load.c  2001/04/19 19:29:50
> @@ -166,6 +166,8 @@
>        report_transfer_performance (callback, data_count, start_time, end_time);
>      }
> 
> +  bfd_cache_close (result_bfd);
> +
>    return result_bfd;
>  }
> 
> Index: sim-utils.c
> ===================================================================
> RCS file: /cvs/cvsfiles/devo/sim/common/sim-utils.c,v
> retrieving revision 1.23
> diff -u -r1.23 sim-utils.c
> --- sim-utils.c 2000/03/02 09:11:13     1.23
> +++ sim-utils.c 2001/04/19 19:29:50
> @@ -287,6 +287,8 @@
>         break;
>        }
> 
> +  bfd_cache_close (prog_bfd);
> +
>    return SIM_RC_OK;
>  }
>


      reply	other threads:[~2001-04-21 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-19 14:01 Frank Ch. Eigler
2001-04-21 15:40 ` Andrew Cagney [this message]

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=3AE20C2B.DC87C56D@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=fche@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    /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