aboutsummaryrefslogtreecommitdiff
path: root/lib/libc
diff options
context:
space:
mode:
authorKyle Evans <kevans@FreeBSD.org>2021-02-08 18:31:17 +0000
committerKyle Evans <kevans@FreeBSD.org>2021-02-08 18:41:22 +0000
commit3e2d96ac974db823255a6f40b90eeffa6e38d022 (patch)
tree24096dab89ab79ea8108e9b175325922a78f65d4 /lib/libc
parent32bf05ad89aaa93f4dd27e3721f4cb52cf57fa03 (diff)
downloadsrc-3e2d96ac974db823255a6f40b90eeffa6e38d022.tar.gz
src-3e2d96ac974db823255a6f40b90eeffa6e38d022.zip
grep: fix -A handling in conjunction with -m match limitation
The basic issue here is that grep, when given -m 1, would stop all line processing once it hit the match count and exit immediately. The problem with exiting immediately is that -A processing only happens when subsequent lines are processed and do not match. The fix here is relatively easy; when bsdgrep matches a line, it resets the 'tail' of the matching context to the value supplied to -A and dumps anything that's been queued up for -B. After the current line has been printed and tail is reset, we check our mcount and do what's needed. Therefore, at the time that we decide we're doing nothing, we know that 'tail' of the context is correct and we can simply continue on if there's still more to pick up. With this change, we still bail out immediately if there's been no -A flag. If -A was supplied, we signal that we should continue on. However, subsequent lines will not even bothere to try and process the line. We have reached the match count, so even if the next line would match then we must process it if it hadn't. Thus, the loop in procfile() can short-circuit and just process the line as a non-match until procmatches() indicates that it's safe to stop. A test has been added to reflect both that we should be picking up the next line and that the next line should be considered a non-match even if it should have been. PR: 253350 MFC-after: 3 days
Diffstat (limited to 'lib/libc')
0 files changed, 0 insertions, 0 deletions