If Tcl_FSGetNormalizedPath is passed a volume-relative
path name, and the volume is not the one where the
working directory resides, it returns the path name
in volume-relative form. The comments in the code
say that it makes it relative to the root of the given
volume, but that's not what actually happens. This
causes considerable surprise, since a normalized
path is supposed to be a unique identifier for a file.
I show below a brief case that demonstrates the problem.
% cd h:
% file norm c:foo
We should be able to design a regression test case
that exhibits the behavior on any system with at least
two drives, but I haven't done so.