| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
make an effort to preserve the ownership and mode of the file we are
editing.
Sponsored by: Registrar AS
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
subtract one unsigned number from another potentially smaller
one, leading to wraparound (and heap corruption, eventually).
PR: 58813
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
whose true and false clauses were equivalent with a check that we are
not about to stumble off the end of the line.
Reported by: peter
Pointy hat to: fanf
|
|
|
|
|
|
|
|
|
| |
There are two bugs: in the s///g case, the substitution didn't occur
at the end of the line; in the s///N case, the code didn't count
forwards along the line properly. See the sg, s3, s4, and s5 tests
in src/tools/regression/usr.bin/sed/.
Reviewed by: tjr
|
|
|
|
| |
Sponsored by: Apple
|
|
|
|
|
|
|
|
| |
line of the pattern space is empty. Don't emit spurious newline when
EOF is reached with the `N' command.
Pointed out by: Oleg Osyka
MFC after: 1 week
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
need to know. Instead, check when we are trying to match a "$" address.
This does not change the way sed processes regular files, but makes it behave
more sensibly when used interactively.
PR: 40101
MFC after: 2 weeks
|
|
|
|
|
|
| |
hold space is null; some functions assume it's never null.
MFC after: 3 days
|
|
|
|
|
|
| |
of the pattern space not to be examined.
Noticed by: Motoyuki Konno <motoyuki@bsdclub.org>
|
|
|
|
| |
command's output so it's the same as what SUSv3 specifies.
|
|
|
|
|
|
|
|
| |
instead add the newline when the pattern space is printed. Make the `G' and
`H' commands add a newline to the space before the data, remove bogus
addition of newline from `x' command.
PR: 29790, 38195
|
| |
|
|
|
|
|
| |
EOL anchor, when the last input line does not end in a newline character.
Picked up by the GNU sed test suite.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
specified, and then the first part of the pattern space is deleted, when
there are two or more input lines, as this results in subtraction of one from
an unsigned integral value of '0'. That bogus value is used in one case
for a loop (that will run far too many times in this case) and a function to
search for a value within a specified range of memory, however now the range
of memory is obscenely large and a segmentation fault will occur. This is
fixed by checking for and appropriately handling a nil pattern space as if
the specified search in memory failed, as indeed it obviously will with nil
pattern space.
Submitted by: Tim J. Robbins <tim@robbins.dropbear.id.au>
PR: bin/34813
Reviewed by: mike
MFC after: 1 day
|
|
|
|
|
|
|
|
|
|
| |
contains a \n.
PR: misc/26153
Submitted by: ashp
Reviewed by: mike
Obtained from: NetBSD
MFC after: 2 days
|
| |
|
|
|
|
| |
Use __FBSDID(), kill register keyword.
|
|
|
|
| |
implementation.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
o main returns int not void
o use return 0 at end of main when needed
o use braces to avoid potentially ambiguous else
o don't default to type int
o #ifdef 0 -> #if 0
Reviewed by: obrien and chuckr
|
| |
|
|
|
|
| |
PR: 6458
|
| |
|
|
|
|
| |
8bit cleanup
|
|
|
|
| |
SCO installation to run all the way through (some POSIX fixes).
|
| |
|
|
|
|
|
|
|
|
|
| |
newline must be part of the pattern space i.e. `echo a|sed -e P' must print
a
a
and not
aa
This is consistent with gnu sed, SunOS, Ultrix (and probably others!)
|
|
|