Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-Id: <4.2.0.58.20010803151214.00bf1840@ics.u-strasbg.fr>
X-Sender: muller AT ics DOT u-strasbg DOT fr
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Fri, 03 Aug 2001 15:15:20 +0200
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
From: Pierre Muller <muller AT cerbere DOT u-strasbg DOT fr>
Subject: Re: Win32 GDB specific problem
Cc: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
In-Reply-To: <996843824.24208.5.camel@lifelesswks>
References: <4 DOT 2 DOT 0 DOT 58 DOT 20010803141303 DOT 01d72780 AT ics DOT u-strasbg DOT fr>
 <4 DOT 2 DOT 0 DOT 58 DOT 20010803141303 DOT 01d72780 AT ics DOT u-strasbg DOT fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit

At 15:04 03/08/01 , Robert Collins a écrit:
>On 03 Aug 2001 14:15:14 +0200, Pierre Muller wrote:
> >    I am one of the persons that wrote the
> > Text Mode IDE for Free Pascal Compiler.
> >
> >    This Text Mode IDE includes GDB inside the executable
> > and it can both compile, run noramlly and debug a
> > given pascal source.
> >
> >    For go32v2 (based on DJGPP) and Linux
> > the repetition of compilation, debugging, editing, recompilation
> > works without problems, but this fails for Win32 version.
> > Once a file as been run under the internal debugger,
> > there is no way to recompile it !
> > Cygwin GDB does have the same problem.
>Have you tried detaching from the process? once the debugger detach's
>the file handle should be rreleased.

No this doesn't change anything !

   Reading carefully the WinAPI documentation,
I saw that only the calling thread can access WaitForDebugEvent.

   Maybe if we start a new threead for each run and exit that thread
after the program is terminated, that would release all handles ?

   I am too bad C and WinAPI programmer to test this out myself :(



Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller AT ics DOT u-strasbg DOT fr
Phone : (33)-3-88-41-40-07  Fax : (33)-3-88-41-40-99

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/