This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: File locking of target executable

From: Andrew Cagney <cagney at gnu dot org>
To: Daniel Jacobowitz <drow at false dot org>,Kris Warkentin <kewarken at qnx dot com>
Cc: "Gdb at Sources dot Redhat dot Com" <gdb at sources dot redhat dot com>
Date: Tue, 02 Mar 2004 15:55:32 -0500
Subject: Re: File locking of target executable
References: <4044F049.6060009@qnx.com> <4044F174.10004@qnx.com> <20040302204402.GA20170@nevyn.them.org>

On Tue, Mar 02, 2004 at 03:41:24PM -0500, Kris Warkentin wrote:

Argh. I always see the answer AFTER I mail to the mailing list. Looks like Windows itself won't let a binary be removed if it's executing. The problem report states that this is happening in the remote case but I just checked and it doesn't seem to be. Must be an error in the bug report.
It can happen in the remote case too sometimes - I don't think Windows
lets you delete an open file either.

Look at bfd_cache_close(), which may solve the problem.

Andrew

Follow-Ups:
- Re: File locking of target executable
  - From: Kris Warkentin

References:
- File locking of target executable
  - From: Kris Warkentin
- Re: File locking of target executable
  - From: Kris Warkentin
- Re: File locking of target executable
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]