path_conv::check() gets confused by recently opened files

Christopher Faylor
Thu May 23 15:25:00 GMT 2002

On Thu, May 23, 2002 at 01:38:04AM -0400, Christopher Faylor wrote:
>On Wed, May 22, 2002 at 02:56:27PM +0200, Corinna Vinschen wrote:
>>I found that path_conv::check() pinches off the tail when searching
>>for existing path components.  This strips the filename here from
>>path_copy since it doesn't exist yet.  The effect is that 
>>path_conv->normalized_path can't be correct when path_conv points
>>to a yet non-existant file.  I don't see an easy way to get the
>>correct normalized path without introducing an additioanl temporary
>>copy of the path.
>I've duplicated the problem.  I'll fix it tomorrow.
>I had to get my gcc working again.  I'm getting random core dumps
>from cygwin now but I think it's gcc related.

Oddly enough, the core dumps were coming from small_vsprintf by way
of fchmod.  Even more oddly, fchmod was using a '%o' format which
was, for some reason not implemented in small_vsprintf.

I can't *believe* that this is the first time that I would have
stumbled across this problem.  The fix was obvious, however.

I did check in another fix for the above problem which seemed almost too
simple.  Please check it out and see if I've broken anything else.  I
hate making changes in the path_conv stuff.


More information about the Cygwin-developers mailing list