Cygwin 1.1.0 gdb troubles
Christopher Jones
cbjones@nortelnetworks.com
Wed Apr 19 10:45:00 GMT 2000
Title: 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
More information about the Cygwin
mailing list