Paths in libc

My "make clean" wasn't working quite right and tracking it down
revealed a bug in src/lib/open.c unlink(). The code was assuming
an absolute path and calling __dotdot() to flatten out the
path. This returned "no entry" errors when trying to remove
relative paths. I put a small patch up for this one on my web
page. However, I think at some point open.c should be gone over
with a fine-toothed comb looking at the path handling stuff.
It seems that many functions duplicate the path processing
logic, and there may be inconsistencies and bugs left. (As
an example, the code in my patch doesn't handle home dir expansion,
although the code in open() does).

Tim N.
Received on 20 Jul 2004 00:00:42 GMT