GNU bug report logs -
#48725
surprising error char/pos with --sandbox + s///e command
Previous Next
To reply to this bug, email your comments to 48725 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-sed <at> gnu.org
:
bug#48725
; Package
sed
.
(Sat, 29 May 2021 04:37:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Travis Everett <travis.a.everett <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-sed <at> gnu.org
.
(Sat, 29 May 2021 04:37:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Not sure this is a bug, but I was a little surprised by the char position
reported by --sandbox errors when there's an s///e command present. (gnu
sed 4.8 via nixpkgs on macOS)
By 1-indexed position, 9 is correct for all 3 commands below, but the last
two indicate 10 and 11 respectively:
$ sed --sandbox -e '{ s/b/c/z }'
sed: -e expression #1, char 9: unknown option to `s'
$ sed --sandbox -e '{ s/b/c/e }'
sed: -e expression #1, char 10: e/r/w commands disabled in sandbox mode
$ sed --sandbox -e '{ s/b/c/e ; s/b/c/e }'
sed: -e expression #1, char 11: e/r/w commands disabled in sandbox mode
It looks like the s command has to be fully consumed before the sandbox
check fails, leaving the error at whatever position technically terminated
the s command?
T
[Message part 2 (text/html, inline)]
This bug report was last modified 3 years and 179 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.