delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/1998/02/06/19:05:41

From: noer AT cygnus DOT com (Geoffrey Noer)
Subject: Re: Changing dll name -> cygwinb19.dll
6 Feb 1998 19:05:41 -0800 :
Message-ID: <199802070221.SAA01950.cygnus.cygwin32.developers@rtl.cygnus.com>
References: <Enyor5 DOT 2Ks AT bbc DOT com>
Reply-To: cygwin32-developers AT cygnus DOT com
To: cygwin32-developers AT cygnus DOT com

Christopher Faylor wrote:
> 
> How about exporting lock_pinfo and unlock_pinfo so ps.cc can use it?
> Then it can lock the process table while it is scanning it and theoretically
> avoid some occasional weird output.

Hmmm...  Not that we don't have other security holes, but this would
mean that anyone could hang Cygwin32 trivially which I don't like very
much.  :-(

I think a better solution here would be to make the process info
available via an exported function(s?) which would take care of the
locking internally.

This may well be not worth the effort, however.

-- 
Geoffrey Noer
noer AT cygnus DOT com

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019