Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Message-ID: From: "Christopher Jones" To: Heribert Dahms , "'cygwin@sourceware.cygnus.com'" Subject: RE: Cygwin 1.1.0 gdb troubles Date: Wed, 19 Apr 2000 09:01:38 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFA9FF.6627193A" X-Orig: ------_=_NextPart_001_01BFA9FF.6627193A Content-Type: text/plain; charset="iso-8859-1" > -----Original Message----- > From: Heribert Dahms [mailto:heribert_dahms@icon-gmbh.de] > Sent: Tuesday, April 18, 2000 6:02 PM > To: 'cygwin@sourceware.cygnus.com' > Subject: RE: Cygwin 1.1.0 gdb troubles > > > Hi Chris, > > it's easy, but is there a guarantee that the format dosen't change? > I remember man ps from HP-UX 10.20 under WARNINGS: > > Users of ps must not rely on the exact field widths and > spacing of > its > output, as these will vary depending on the system, the > release of > HP-UX, and the data to be displayed. > 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? Brian ------_=_NextPart_001_01BFA9FF.6627193A Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Cygwin 1.1.0 gdb troubles

> -----Original Message-----
> From: Heribert Dahms [mailto:heribert_dahms@icon-g= mbh.de]
> Sent: Tuesday, April 18, 2000 6:02 PM
> To: 'cygwin@sourceware.cygnus.com'
> Subject: RE: Cygwin 1.1.0 gdb troubles
>
>
> Hi Chris,
>
> it's easy, but is there a guarantee that the = format dosen't change?
> I remember man ps from HP-UX 10.20 under = WARNINGS:
>
>       Users of ps = must not rely on the exact field widths and
> spacing of
> its
>       output, as = these will vary depending on the system, the
> release of
>       HP-UX, and = the data to be displayed.
>

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?

Brian

------_=_NextPart_001_01BFA9FF.6627193A--