GNU bug report logs -
#69437
basename fails with suffix containing slash
Previous Next
Reported by: Zefram <zefram <at> fysh.org>
Date: Tue, 27 Feb 2024 20:26:03 UTC
Severity: normal
Done: Rob Browning <rlb <at> defaultvalue.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
$ guile-3.0.9 -c '(write (basename "foo/bar" "o/bar")) (newline)'
Backtrace:
[...]
ERROR: In procedure basename:
Value out of range: 18446744073709551614
Looks like this decides based on the whole pathname that the
five-character suffix matches, and then tries to remove that suffix
from the three-character basename. This is not sensible behaviour.
It should probably signal an error if given any suffix argument that
contains a slash character. If not, then it should be comparing the
suffix against the basename, not the complete pathname, with the effect
that a suffix containing a slash will never be matched and so no attempt
will be made to remove it.
-zefram
This bug report was last modified 287 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.