Revision: 502
http://vcs.pcre.org/viewvc?view=rev&revision=502
Author: ph10
Date: 2010-03-07 12:05:20 +0000 (Sun, 07 Mar 2010)
Log Message:
-----------
Add crossreference from pcreperform to pcrestack.
Modified Paths:
--------------
code/trunk/doc/pcreperform.3
Modified: code/trunk/doc/pcreperform.3
===================================================================
--- code/trunk/doc/pcreperform.3 2010-03-07 11:49:54 UTC (rev 501)
+++ code/trunk/doc/pcreperform.3 2010-03-07 12:05:20 UTC (rev 502)
@@ -8,14 +8,15 @@
time. The way you express your pattern as a regular expression can affect both
of them.
.
-.SH "MEMORY USAGE"
+.SH "COMPILED PATTERN MEMORY USAGE"
.rs
.sp
Patterns are compiled by PCRE into a reasonably efficient byte code, so that
most simple patterns do not use much memory. However, there is one case where
-memory usage can be unexpectedly large. When a parenthesized subpattern has a
-quantifier with a minimum greater than 1 and/or a limited maximum, the whole
-subpattern is repeated in the compiled code. For example, the pattern
+the memory usage of a compiled pattern can be unexpectedly large. If a
+parenthesized subpattern has a quantifier with a minimum greater than 1 and/or
+a limited maximum, the whole subpattern is repeated in the compiled code. For
+example, the pattern
.sp
(abc|def){2,4}
.sp
@@ -63,6 +64,21 @@
speed is acceptable, this kind of rewriting will allow you to process patterns
that PCRE cannot otherwise handle.
.
+.
+.SH "STACK USAGE AT RUN TIME"
+.rs
+.sp
+When \fBpcre_exec()\fP is used for matching, certain kinds of pattern can cause
+it to use large amounts of the process stack. In some environments the default
+process stack is quite small, and if it runs out the result is often SIGSEGV.
+This issue is probably the most frequently raised problem with PCRE. Rewriting
+your pattern can often help. The
+.\" HREF
+\fBpcrestack\fP
+.\"
+documentation discusses this issue in detail.
+.
+.
.SH "PROCESSING TIME"
.rs
.sp
@@ -148,6 +164,6 @@
.rs
.sp
.nf
-Last updated: 06 March 2007
-Copyright (c) 1997-2007 University of Cambridge.
+Last updated: 07 March 2010
+Copyright (c) 1997-2010 University of Cambridge.
.fi
