This is the mail archive of the
mailing list for the Cygwin project.
Re: Cygwin 1.1.0 gdb troubles
- To: "'cygwin at sourceware dot cygnus dot com'" <cygwin at sourceware dot cygnus dot com>
- Subject: Re: Cygwin 1.1.0 gdb troubles
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Wed, 19 Apr 2000 12:47:24 -0400
- References: <C9A8E1D07093D111B76A0000F8C9918A03332F3D@zrtpd003.us.nortel.com>
- Reply-To: cygwin at sourceware dot cygnus dot com
On Wed, Apr 19, 2000 at 09:01:38AM -0400, Christopher Jones wrote:
>Seems like it would make more sense to at least hide these cygwin pids
>and let users always use windows pids for ps, kill, $$ in a shell, etc.
>So the PID and PPID values would be the real windows values and cygwin
>pids would disappear into the internals somewhere... probably a lookup
>table if you really need to have them still. Something like this would
>be more seemless, wouldn't it?
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.
Want to unsubscribe from this list?
Send a message to email@example.com