Date: Mon, 27 Feb 2006 13:07:44 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: d_ino bug in //
Message-ID: <20060227180744.GA10711@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <022720061758 DOT 2378 DOT 44033DDA000153AC0000094A22073007930A050E040D0C079D0A AT comcast DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <022720061758.2378.44033DDA000153AC0000094A22073007930A050E040D0C079D0A@comcast.net>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Mon, Feb 27, 2006 at 05:58:50PM +0000, Eric Blake wrote:
>> >It looks like d_ino is not being correctly populated within //.
>> >Running the program below on snapshot 20060220 produced:
>> 
>> A (somewhat) simple test case (patent pending) is nice but it really
>> should be accompanied with an explanation of the problem.  How about
>> describing *in words* what you think is broken?
>
>It looks like Corinna already nailed the issue, but for the archive's
>sake, my complaint was that under //, d_ino and st_ino did not match
>properly.

Thanks for the explanation.

It would really be nice (tm) if we had someone devoted to developing test
suite applications for testing these type of things so that we could be
assured of no regressions.

Anyone interested in being the test suite go-to person?

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/