public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Christopher Jones" <cbjones@nortelnetworks.com>
To: Heribert Dahms <heribert_dahms@icon-gmbh.de>,
	"'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>
Subject: RE: Cygwin 1.1.0 gdb troubles
Date: Wed, 19 Apr 2000 06:02:00 -0000	[thread overview]
Message-ID: <C9A8E1D07093D111B76A0000F8C9918A03332F3D@zrtpd003.us.nortel.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]

Title: RE: Cygwin 1.1.0 gdb troubles







> -----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




             reply	other threads:[~2000-04-19  6:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-19  6:02 Christopher Jones [this message]
2000-04-19  7:15 ` Re[2]: " Paul Sokolovsky
2000-04-19  7:22   ` DJ Delorie
2000-04-19 12:19     ` Re[2]: " Paul Sokolovsky
2000-04-19 12:31       ` DJ Delorie
2000-04-19 16:27       ` Chris Faylor
2000-04-19 10:05   ` Chris Faylor
2000-04-20 23:37     ` Re[2]: " Paul Sokolovsky
2000-04-21  8:08       ` Chris Faylor
2000-04-19  9:47 ` Chris Faylor
  -- strict thread matches above, loose matches on Subject: below --
2000-04-19 10:45 Christopher Jones
2000-04-19 10:49 ` Chris Faylor
2000-04-18 15:04 Heribert Dahms
2000-04-18 14:32 Heribert Dahms
2000-04-18 14:39 ` Chris Faylor
2000-04-18 14:11 Heribert Dahms
2000-04-18 14:26 ` Chris Faylor
2000-04-17 21:32 Boyd Adamson
2000-04-17 21:47 ` Chris Faylor
2000-04-17 22:30   ` Chris Faylor
2000-04-17 23:41     ` Boyd Adamson
2000-04-18 12:29       ` Chris Faylor
2000-04-18  6:12   ` Tim Prince
2000-04-18 13:17     ` Chris Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C9A8E1D07093D111B76A0000F8C9918A03332F3D@zrtpd003.us.nortel.com \
    --to=cbjones@nortelnetworks.com \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=heribert_dahms@icon-gmbh.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).