Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Thu, 14 Sep 2000 17:37:07 +0100 Message-ID: <2181-Thu14Sep2000173707+0100-starksb@ebi.ac.uk> X-Mailer: emacs 20.7.1 (via feedmail 9-beta-7 I); VM 6.75 under Emacs 20.7.1 From: David Starks-Browning MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: DJ Delorie CC: cygwin-developers AT sources DOT redhat DOT com Subject: Re: path bug in cygcheck? In-Reply-To: <200009141509.LAA04701@envy.delorie.com> References: <1341-Thu14Sep2000140817+0100-starksb AT ebi DOT ac DOT uk> <8773-Thu14Sep2000153640+0100-starksb AT ebi DOT ac DOT uk> <200009141509 DOT LAA04701 AT envy DOT delorie DOT com> On Thursday 14 Sep 00, DJ Delorie writes: > > > I would say this is a defect, albeit a minor one, and perhaps not > > worth fixing. > > In cygcheck, *all* bugs are worth fixing. This is one of the few > programs that absolutely *must* do the right thing, because we use it > to diagnose user problems. In that case, I think that cygcheck.cc will require two separate path lists, one for searching programs and one for searching dll's. The current problem stems from using the same data structure to serve both purposes. I would volunteer to have a go at this, but it would be some weeks before I could get started. Cheers, David