This is the mail archive of the
mailing list for the Cygwin project.
Re: Cygwin 1.1.0 gdb troubles
- To: "Christopher Jones" <cbjones at nortelnetworks dot com>
- Subject: Re: Cygwin 1.1.0 gdb troubles
- From: Paul Sokolovsky <paul-ml at is dot lg dot ua>
- Date: Wed, 19 Apr 2000 16:53:38 +0300
- CC: cygwin at sourceware dot cygnus dot com
- References: <C9A8E1D07093D111B76A0000F8C9918A03332F3D@zrtpd003.us.nortel.com>
- Reply-To: Paul Sokolovsky <paul-ml at is dot lg dot ua>
Christopher Jones <firstname.lastname@example.org> wrote:
CJ> Seems like it would make more sense to at least hide these cygwin pids and
CJ> let users always use windows pids for ps, kill, $$ in a shell, etc. So the
CJ> PID and PPID values would be the real windows values and cygwin pids would
CJ> disappear into the internals somewhere... probably a lookup table if you
CJ> really need to have them still. Something like this would be more seemless,
CJ> wouldn't it?
If no cygwin people will agree with you, then at least me will.
IMHO, win32 is undoubtfully POSIX by spirit, only having somewhat
twisted upbringing. Almost any POSIX feature maps one-to-one to win32
one and difference is only in some idiosyncratic details. As an
example, DeleteFile() does exactly what remove() does with one
difference: remove() explicitly states possibility of removing opened
file, while DeleteFile() explicitly prohibits it. I can't believe
there's some adequate reasoning behind DeleteFile()'s behaviour. I
just can imagine some win32 architect reading POSIX spec and time to
time exclaiming: 'And *here*, we'll do vice-versa!' ;-)
Well, what idiosyncratic features of native pids would harden
their usage as POSIX pisd as-is?
1. While NT's pids are rather POSIX-correct as-is, 9x's ones are
negative values, large (up to 10 dec digits) by module.
2. There's no documented way to get ppid on NT.
3. It's impossible to overlay image of current process. This means,
when performing usual fork-exec chain, there will be three processes:
parent, exec() implementer stub and execed child. So, between child
and parent in POSIX terms there will be other process.
While these problems may seem denying original idea, they hardly
do. The workarounds for them exist, working and confidently may be
called more robust than maintaining additional superstructures,
moreover shared between all processes.
Well, *that*'s not most annoying feature of cygwin. Just net
version ago there might arise problems with just having cygwin work
properly after installation, mostly because ungrounded default mount
table setup. But look - this version now takes care to ask user where
he wants having root mount. So, all consistently improving and maybe
one day other areas also will be addressed.
Paul Sokolovsky, IT Specialist
Want to unsubscribe from this list?
Send a message to email@example.com