| 77 |
subject strings is to write repeated parenthesized subpatterns to match more |
subject strings is to write repeated parenthesized subpatterns to match more |
| 78 |
than one character whenever possible. |
than one character whenever possible. |
| 79 |
</P> |
</P> |
| 80 |
|
<br><b> |
| 81 |
|
Compiling PCRE to use heap instead of stack |
| 82 |
|
</b><br> |
| 83 |
<P> |
<P> |
| 84 |
In environments where stack memory is constrained, you might want to compile |
In environments where stack memory is constrained, you might want to compile |
| 85 |
PCRE to use heap memory instead of stack for remembering back-up points. This |
PCRE to use heap memory instead of stack for remembering back-up points. This |
| 94 |
same, and are always freed in reverse order, it may be possible to implement |
same, and are always freed in reverse order, it may be possible to implement |
| 95 |
customized memory handlers that are more efficient than the standard functions. |
customized memory handlers that are more efficient than the standard functions. |
| 96 |
</P> |
</P> |
| 97 |
|
<br><b> |
| 98 |
|
Limiting PCRE's stack usage |
| 99 |
|
</b><br> |
| 100 |
|
<P> |
| 101 |
|
PCRE has an internal counter that can be used to limit the depth of recursion, |
| 102 |
|
and thus cause <b>pcre_exec()</b> to give an error code before it runs out of |
| 103 |
|
stack. By default, the limit is very large, and unlikely ever to operate. It |
| 104 |
|
can be changed when PCRE is built, and it can also be set when |
| 105 |
|
<b>pcre_exec()</b> is called. For details of these interfaces, see the |
| 106 |
|
<a href="pcrebuild.html"><b>pcrebuild</b></a> |
| 107 |
|
and |
| 108 |
|
<a href="pcreapi.html"><b>pcreapi</b></a> |
| 109 |
|
documentation. |
| 110 |
|
</P> |
| 111 |
|
<P> |
| 112 |
|
As a very rough rule of thumb, you should reckon on about 500 bytes per |
| 113 |
|
recursion. Thus, if you want to limit your stack usage to 8Mb, you |
| 114 |
|
should set the limit at 16000 recursions. A 64Mb stack, on the other hand, can |
| 115 |
|
support around 128000 recursions. The <b>pcretest</b> test program has a command |
| 116 |
|
line option (<b>-S</b>) that can be used to increase the size of its stack. |
| 117 |
|
</P> |
| 118 |
|
<br><b> |
| 119 |
|
Changing stack size in Unix-like systems |
| 120 |
|
</b><br> |
| 121 |
<P> |
<P> |
| 122 |
In Unix-like environments, there is not often a problem with the stack unless |
In Unix-like environments, there is not often a problem with the stack unless |
| 123 |
very long strings are involved, though the default limit on stack size varies |
very long strings are involved, though the default limit on stack size varies |
| 139 |
attempts to increase the soft limit to 100Mb using <b>setrlimit()</b>. You must |
attempts to increase the soft limit to 100Mb using <b>setrlimit()</b>. You must |
| 140 |
do this before calling <b>pcre_exec()</b>. |
do this before calling <b>pcre_exec()</b>. |
| 141 |
</P> |
</P> |
| 142 |
|
<br><b> |
| 143 |
|
Changing stack size in Mac OS X |
| 144 |
|
</b><br> |
| 145 |
<P> |
<P> |
| 146 |
PCRE has an internal counter that can be used to limit the depth of recursion, |
Using <b>setrlimit()</b>, as described above, should also work on Mac OS X. It |
| 147 |
and thus cause <b>pcre_exec()</b> to give an error code before it runs out of |
is also possible to set a stack size when linking a program. There is a |
| 148 |
stack. By default, the limit is very large, and unlikely ever to operate. It |
discussion about stack sizes in Mac OS X at this web site: |
| 149 |
can be changed when PCRE is built, and it can also be set when |
<a href="http://developer.apple.com/qa/qa2005/qa1419.html">http://developer.apple.com/qa/qa2005/qa1419.html.</a> |
|
<b>pcre_exec()</b> is called. For details of these interfaces, see the |
|
|
<a href="pcrebuild.html"><b>pcrebuild</b></a> |
|
|
and |
|
|
<a href="pcreapi.html"><b>pcreapi</b></a> |
|
|
documentation. |
|
|
</P> |
|
|
<P> |
|
|
As a very rough rule of thumb, you should reckon on about 500 bytes per |
|
|
recursion. Thus, if you want to limit your stack usage to 8Mb, you |
|
|
should set the limit at 16000 recursions. A 64Mb stack, on the other hand, can |
|
|
support around 128000 recursions. The <b>pcretest</b> test program has a command |
|
|
line option (<b>-S</b>) that can be used to increase the size of its stack. |
|
| 150 |
</P> |
</P> |
| 151 |
<br><b> |
<br><b> |
| 152 |
AUTHOR |
AUTHOR |
| 163 |
REVISION |
REVISION |
| 164 |
</b><br> |
</b><br> |
| 165 |
<P> |
<P> |
| 166 |
Last updated: 05 June 2007 |
Last updated: 09 July 2008 |
| 167 |
<br> |
<br> |
| 168 |
Copyright © 1997-2007 University of Cambridge. |
Copyright © 1997-2008 University of Cambridge. |
| 169 |
<br> |
<br> |
| 170 |
<p> |
<p> |
| 171 |
Return to the <a href="index.html">PCRE index page</a>. |
Return to the <a href="index.html">PCRE index page</a>. |