Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: From: "Christopher Jones" To: cygwin AT sourceware DOT cygnus DOT com Subject: RE: Cygwin 1.1.0 gdb troubles Date: Wed, 19 Apr 2000 13:44:53 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFAA26.FC678E6C" ------_=_NextPart_001_01BFAA26.FC678E6C Content-Type: text/plain; charset="iso-8859-1" > > The main reason for cygwin pids is that there is no corresponding > exec*() style interface in Win32 land. Most programs which > use fork/exec > also rely on the fact that the exec'ed process has the same PID as the > fork. There is no way to do this using the Win32 API. Thanks for the explanation Chris. It had been a while since I dealt with fork/exec and I'd forgotten how much they rely on a certain PID behavior. So the only other way to go would be to assign win32 processes cygwin pids which would probably lead to more yuckiness; and maybe there is not a way to muck with the internals of windows such that cygwin is always resident and receiving notification of new win32 process/thread creation. Ick. Oh well. :) Brian ------_=_NextPart_001_01BFAA26.FC678E6C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Cygwin 1.1.0 gdb troubles

>
> The main reason for cygwin pids is that there = is no corresponding
> exec*() style interface in Win32 land.  = Most programs which
> use fork/exec
> also rely on the fact that the exec'ed process = has the same PID as the
> fork.  There is no way to do this using = the Win32 API.

Thanks for the explanation Chris.  It had been a = while since I dealt with fork/exec and I'd forgotten how much they rely = on a certain PID behavior.  So the only other way to go would be = to assign win32 processes cygwin pids which would probably lead to more = yuckiness; and maybe there is not a way to muck with the internals of = windows such that cygwin is always resident and receiving notification = of new win32 process/thread creation.  Ick.  Oh well.  = :)

Brian

------_=_NextPart_001_01BFAA26.FC678E6C--