diff options
author | ph10 <ph10@6239d852-aaf2-0410-a92c-79f79f948069> | 2016-11-22 15:37:02 +0000 |
---|---|---|
committer | ph10 <ph10@6239d852-aaf2-0410-a92c-79f79f948069> | 2016-11-22 15:37:02 +0000 |
commit | b55d9179309bb3b6ba08c92d279555b2f897be69 (patch) | |
tree | 82b77499d37f9a1b91d3e322ea285f5ccaab4c78 /doc/html/pcre2build.html | |
parent | 981381ae1c1c3924bbb76541aa169b742bee0cd6 (diff) | |
download | pcre2-b55d9179309bb3b6ba08c92d279555b2f897be69.tar.gz |
Add pcre2_code_copy_with_tables().
git-svn-id: svn://vcs.exim.org/pcre2/code/trunk@605 6239d852-aaf2-0410-a92c-79f79f948069
Diffstat (limited to 'doc/html/pcre2build.html')
-rw-r--r-- | doc/html/pcre2build.html | 55 |
1 files changed, 40 insertions, 15 deletions
diff --git a/doc/html/pcre2build.html b/doc/html/pcre2build.html index 6c8e1de..13ae9cb 100644 --- a/doc/html/pcre2build.html +++ b/doc/html/pcre2build.html @@ -34,9 +34,10 @@ please consult the man page, in case the conversion went wrong. <li><a name="TOC19" href="#SEC19">INCLUDING DEBUGGING CODE</a> <li><a name="TOC20" href="#SEC20">DEBUGGING WITH VALGRIND SUPPORT</a> <li><a name="TOC21" href="#SEC21">CODE COVERAGE REPORTING</a> -<li><a name="TOC22" href="#SEC22">SEE ALSO</a> -<li><a name="TOC23" href="#SEC23">AUTHOR</a> -<li><a name="TOC24" href="#SEC24">REVISION</a> +<li><a name="TOC22" href="#SEC22">SUPPORT FOR FUZZERS</a> +<li><a name="TOC23" href="#SEC23">SEE ALSO</a> +<li><a name="TOC24" href="#SEC24">AUTHOR</a> +<li><a name="TOC25" href="#SEC25">REVISION</a> </ul> <br><a name="SEC1" href="#TOC1">BUILDING PCRE2</a><br> <P> @@ -376,16 +377,19 @@ they are not. <P> <b>pcre2grep</b> uses an internal buffer to hold a "window" on the file it is scanning, in order to be able to output "before" and "after" lines when it -finds a match. The size of the buffer is controlled by a parameter whose -default value is 20K. The buffer itself is three times this size, but because -of the way it is used for holding "before" lines, the longest line that is -guaranteed to be processable is the parameter size. You can change the default -parameter value by adding, for example, +finds a match. The starting size of the buffer is controlled by a parameter +whose default value is 20K. The buffer itself is three times this size, but +because of the way it is used for holding "before" lines, the longest line that +is guaranteed to be processable is the parameter size. If a longer line is +encountered, <b>pcre2grep</b> automatically expands the buffer, up to a +specified maximum size, whose default is 1M or the starting size, whichever is +the larger. You can change the default parameter values by adding, for example, <pre> - --with-pcre2grep-bufsize=50K + --with-pcre2grep-bufsize=51200 + --with-pcre2grep-max-bufsize=2097152 </pre> -to the <b>configure</b> command. The caller of \fPpcre2grep\fP can override this -value by using --buffer-size on the command line. +to the <b>configure</b> command. The caller of \fPpcre2grep\fP can override +these values by using --buffer-size and --max-buffer-size on the command line. </P> <br><a name="SEC18" href="#TOC1">PCRE2TEST OPTION FOR LIBREADLINE SUPPORT</a><br> <P> @@ -497,11 +501,32 @@ This cleans all coverage data including the generated coverage report. For more information about code coverage, see the <b>gcov</b> and <b>lcov</b> documentation. </P> -<br><a name="SEC22" href="#TOC1">SEE ALSO</a><br> +<br><a name="SEC22" href="#TOC1">SUPPORT FOR FUZZERS</a><br> +<P> +There is a special option for use by people who want to run fuzzing tests on +PCRE2: +<pre> + --enable-fuzz-support +</pre> +At present this applies only to the 8-bit library. If set, it causes an extra +library called libpcre2-fuzzsupport.a to be built, but not installed. This +contains a single function called LLVMFuzzerTestOneInput() whose arguments are +a pointer to a string and the length of the string. When called, this function +tries to compile the string as a pattern, and if that succeeds, to match it. +This is done both with no options and with some random options bits that are +generated from the string. Setting --enable-fuzz-support also causes a binary +called <b>pcre2fuzzcheck</b> to be created. This is normally run under valgrind +or used when PCRE2 is compiled with address sanitizing enabled. It calls the +fuzzing function and outputs information about it is doing. The input strings +are specified by arguments: if an argument starts with "=" the rest of it is a +literal input string. Otherwise, it is assumed to be a file name, and the +contents of the file are the test string. +</P> +<br><a name="SEC23" href="#TOC1">SEE ALSO</a><br> <P> <b>pcre2api</b>(3), <b>pcre2-config</b>(3). </P> -<br><a name="SEC23" href="#TOC1">AUTHOR</a><br> +<br><a name="SEC24" href="#TOC1">AUTHOR</a><br> <P> Philip Hazel <br> @@ -510,9 +535,9 @@ University Computing Service Cambridge, England. <br> </P> -<br><a name="SEC24" href="#TOC1">REVISION</a><br> +<br><a name="SEC25" href="#TOC1">REVISION</a><br> <P> -Last updated: 01 April 2016 +Last updated: 01 November 2016 <br> Copyright © 1997-2016 University of Cambridge. <br> |