Tcl Source Code

The Tcl_FSNormalizePathProc of a 
Tcl_Filesystem gets three arguments,

  (TclInterp *interp,
   Tcl_Obj *pathPtr,
   int nextCheckPoint)

and an int return value.

It's spelled out in in the Tcl_Filesystem
docs that both nextCheckPoint and
the returned value should be indices
into the pathPtr->bytes array and the
value should point to either the start
(0) the end (bytes[cp] == '\0') or
to a separator character, usually '/'.

The unix TclpObjNormalizePath()
routine does not follow these rules;
it returns a value that points "one past"
the separator, not to it.

The correction is simple, just remove
lines 1805-1807 from unix/tclUnixFCmd.c
Those lines incorrectly advance the
checkpoint value one past where it
ought to be.

Removing those lines leads to no
new failures in the test suite on three
different unix systems I tried.

Logged In: YES 
user_id=32170

Oh yes, I would commit the simpler one now (no 'access'
check), but consider adding the other check in place if/when
the needs of the other discussions/fixes require it.

Logged In: YES 
user_id=80530

which one?

The additional access() call
is helpful when there are
other FS's registered, as it
will let the native FS claim
the entire path when it can.

However, when there's only
a native FS around, the
additional access() call
adds to the overhead of path
normaliztaion.

Intermingled with this is
Bug 931847.  The plans
for revising Tcl_FSNTUP
might influence the choice.

Logged In: YES 
user_id=32170

Please do commit the fix.

File Added - 84878: 941108.patch

Logged In: YES 
user_id=80530


Even better, in addition to removing
those lines, it appears that 
TclpObjNormalizePath can claim
to have normalized the whole thing
rather than just all but the final
component via this patch.