From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18765 invoked by alias); 2 Mar 2004 21:08:23 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 18754 invoked from network); 2 Mar 2004 21:08:22 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sources.redhat.com with SMTP; 2 Mar 2004 21:08:22 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id QAA02303 for ; Tue, 2 Mar 2004 16:24:38 -0500 Received: from qnx.com ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with ESMTP id PAA25974 for ; Tue, 2 Mar 2004 15:35:15 -0500 Message-ID: <4044F049.6060009@qnx.com> Date: Tue, 02 Mar 2004 21:08:00 -0000 From: Kris Warkentin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 MIME-Version: 1.0 To: "Gdb@Sources.Redhat.Com" Subject: File locking of target executable Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-03/txt/msg00018.txt.bz2 I've observed (on Windows at least) that when I'm debugging an executable, I can't delete it. Just having it the executable loaded in gdb is insufficient; it actually has to be running. I didn't see anything on a casual sniff through the source but perhaps I'm missing some sort of lock procedure. This comes up in the context of Eclipse: if you're debugging a project and try to rebuild, the make fails when it can't unlink the target app. It looks like under some circumstances gdb might use memory mapped files...could that be the culprit? cheers, Kris