| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fix a ton of speelling errors
|
|
|
|
|
|
|
|
|
| |
sed: Bounds check the file path used in the 'w' command.
Modified version of a diff from Sebastien Marie to prevent a crash found
with the afl fuzzer.
Obtained from: OpenBSD (CVS Rev. 1.37)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Per the resolution of POSIX bug 0000779 (note 0002050) add support for using 'i'
as a case insensitive flag.
Add regression test for recently added 'i' flag in r259132.
the i modifier was added in r259132 since POSIX recently agreed to add
it. Switch uses of /I to /i.
PR: standards/184641
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"The escape sequence '\n' shall match a <newline> embedded in
the pattern space."
It is unclear whether this also applies to a \n embedded in a
character class. Disable the existing handling of \n in a character
class following Mac OS X, GNU sed version 4.1.5 with --posix, and
SunOS 5.10 /usr/bin/sed.
Pointed by: Marius Strobl
Obtained from: Mac OS X
|
|
|
|
|
|
|
|
|
|
|
| |
of the y (translate) command.
"If a backslash character is immediately followed by a backslash
character in string1 or string2, the two backslash characters shall
be counted as a single literal backslash character"
Pointed by: Marius Strobl
Obtained from: Mac OS X
|
|
|
|
|
| |
Pointed by: Marius Strobl
Obtained from: Apple
|
|
|
|
|
| |
PR: 134856
Submitted by: Jeremie Le Hen - jeremie at le-hen dot org
|
|
|
|
|
|
|
|
|
|
| |
specification and regression test regress:25.
"A function can be preceded by one or more '!' characters, in which
case the function shall be applied if the addresses do not select
the pattern space."
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
| |
parenthesized subexpression is defined. For example, the
following command line caused unexpected behavior like
segmentation fault:
% echo test | sed -e 's/test/\1/'
PR: bin/126682
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
1) Add missing parens around assignment that is compared to zero.
2) Make some variables that only take non-negative values unsigned.
3) Some casts/type changes to fix other constness warnings.
4) Make one variable a const char *.
5) Make sure termwidth is positive, it doesn't make sense for it to be negative.
Approved by: dds
|
|
|
|
|
|
|
|
|
|
|
| |
whether we should ignore case, determine the flag by calling
compile_flags() first. Also, make sure that we obtain an
initialized cmd->u.s buffer before processing further. We
may want to refine this solution later, but for now, make
the changes in order to unbreak world build after a sed(1)
with rev. 1.29 of compile.c is installed.
Approved by: re (hrs)
|
|
|
|
|
|
|
|
|
| |
For example,
sed /foo/Id
sed s/foo/bar/Ig
Reviewed by: dds
Approved by: re (hrs)
|
|
|
|
|
|
|
|
| |
cause the next substitute flag to be ignored.
While working at it, detect and report overflows.
Reported by: Jingsong Liu
MFC after: 1 week
|
| |
|
|
|
|
|
|
| |
software (original contributor).
Reviewed by: imp
|
| |
|
| |
|
| |
|
|
|
|
| |
Obtained from: NetBSD (kleink, Aymeric Vincent)
|
|
|
|
|
|
|
| |
was initiated at the last character of the line buffer, the Wrong
Thing was done and sed barfed by interpreting the following NUL byte
as a digit. Instead, pull up the next buffer and record that the "\"
was last seen.
|
|
|
|
|
|
|
|
| |
substitution expressions in the form `s,[fooexp],[barexp],;...' treated
as invalid when the third `,' is (_POSIX2_LINE_MAX * N)-th character in
the line.
MFC after: 2 weeks
|
| |
|
|
|
|
| |
Use __FBSDID(), kill register keyword.
|
|
|
|
|
| |
PR: bin/11900
MFC after: 2 weeks
|
|
|
|
| |
implementation.
|
|
|
|
|
|
|
|
|
| |
Testcase:
echo FOO | sed "/FOO/c\\
`jot -b 'aaaa\' 500`"
Submitted by: Max Khon <fjoe@newst.net>
|
| |
|
| |
|
| |
|
|
|
|
| |
PR: bin/7939
|
|
|
|
|
|
|
| |
an ``a'' command that has an escaped newline on the
last line of the last script that we're processing.
This fixes exmh2/scripts/build when /etc/malloc.conf -> AJ
|
| |
|
|
|
|
| |
8bit cleanup
|
|
|
|
|
|
|
|
|
|
|
|
| |
The fundamental problem with the original code is that it accesses
p[-2] which is one before the beginning of the input buffer for
empty lines. rev.1.6 just moved the problem from failures when
p[-2] happens to be '\\' to failures when it happens to be '\0'.
rev.1.5 was confused about the trailing newline and other things.
I went back to rev.1.5 and fixed it. The result is the same as
Keith Bostic's final version in PR 1356 except it loses more
gracefully for excessively long input lines.
|
|
|
|
|
|
| |
introduced a new bug. This fix appears to work correctly. Fixes PR#1350.
Submitted by: mark@linus.demon.co.uk (Mark Valentine)
|
|
|
|
|
|
| |
continuation lines.
Submitted by: Keith Bostic via Kirk McKusick
|
|
|
|
| |
SCO installation to run all the way through (some POSIX fixes).
|
| |
|
|
|
|
|
|
| |
doesn't initialize malloced structure.
Submitted by: vode@hut.fi
|
|
|