| delorie.com/archives/browse.cgi | search |
| Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
| List-Subscribe: | <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com> |
| List-Archive: | <http://sourceware.cygnus.com/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT sourceware DOT cygnus DOT com> |
| List-Help: | <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs> |
| Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
| Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
| Message-ID: | <C9A8E1D07093D111B76A0000F8C9918A03333088@zrtpd003.us.nortel.com> |
| From: | "Christopher Jones" <cbjones AT nortelnetworks DOT com> |
| 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) |
------_=_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 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2651.65"> <TITLE>RE: Cygwin 1.1.0 gdb troubles</TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> The main reason for cygwin pids is that there = is no corresponding</FONT> <BR><FONT SIZE=3D2>> exec*() style interface in Win32 land. = Most programs which </FONT> <BR><FONT SIZE=3D2>> use fork/exec</FONT> <BR><FONT SIZE=3D2>> also rely on the fact that the exec'ed process = has the same PID as the</FONT> <BR><FONT SIZE=3D2>> fork. There is no way to do this using = the Win32 API.</FONT> </P> <P><FONT SIZE=3D2>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. = :)</FONT></P> <P><FONT SIZE=3D2>Brian</FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01BFAA26.FC678E6C--
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |