Mail Archives: cygwin/2000/04/19/08:02:58
------_=_NextPart_001_01BFA9FF.6627193A
Content-Type: text/plain;
charset="iso-8859-1"
> -----Original Message-----
> From: Heribert Dahms [mailto:heribert_dahms AT icon-gmbh DOT de]
> Sent: Tuesday, April 18, 2000 6:02 PM
> To: 'cygwin AT sourceware DOT cygnus DOT 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
<!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>
<BR>
<BR>
<P><FONT SIZE=3D2>> -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>> From: Heribert Dahms [<A =
HREF=3D"mailto:heribert_dahms AT icon-gmbh DOT de">mailto:heribert_dahms AT icon-g=
mbh.de</A>]</FONT>
<BR><FONT SIZE=3D2>> Sent: Tuesday, April 18, 2000 6:02 PM</FONT>
<BR><FONT SIZE=3D2>> To: 'cygwin AT sourceware DOT cygnus DOT com'</FONT>
<BR><FONT SIZE=3D2>> Subject: RE: Cygwin 1.1.0 gdb troubles</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Hi Chris,</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> it's easy, but is there a guarantee that the =
format dosen't change?</FONT>
<BR><FONT SIZE=3D2>> I remember man ps from HP-UX 10.20 under =
WARNINGS:</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Users of ps =
must not rely on the exact field widths and </FONT>
<BR><FONT SIZE=3D2>> spacing of</FONT>
<BR><FONT SIZE=3D2>> its</FONT>
<BR><FONT SIZE=3D2>> output, as =
these will vary depending on the system, the </FONT>
<BR><FONT SIZE=3D2>> release of</FONT>
<BR><FONT SIZE=3D2>> HP-UX, and =
the data to be displayed.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
</P>
<P><FONT SIZE=3D2>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?</FONT></P>
<P><FONT SIZE=3D2>Brian</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01BFA9FF.6627193A--
- Raw text -