Lines Matching full:stack
16 PCRE DISCUSSION OF STACK USAGE
40 <b>pcre_dfa_exec()</b> to run out of stack. At present, there is no protection
48 Reducing <b>pcre_exec()</b>'s stack usage
52 from the process stack. For certain kinds of pattern and data, very large
53 amounts of stack may be needed, despite the recognition of "tail recursion".
54 You can often reduce the amount of recursion, and therefore the amount of stack
64 parenthesis is processed, a recursion occurs, so this formulation uses a stack
65 frame for each matched character. For a long string, a lot of stack is
71 This uses very much less stack, because runs of characters that do not contain
76 stack usage.
79 This example shows that one way of avoiding stack problems when matching long
84 Compiling PCRE to use heap instead of stack for <b>pcre_exec()</b>
87 In environments where stack memory is constrained, you might want to compile
88 PCRE to use heap memory instead of stack for remembering back-up points when
92 documentation. When built in this way, instead of using the stack, PCRE obtains
101 Limiting <b>pcre_exec()</b>'s stack usage
107 stack. The default values of the limits are very large, and unlikely ever to
119 recursion. Thus, if you want to limit your stack usage to 8Mb, you
120 should set the limit at 16000 recursions. A 64Mb stack, on the other hand, can
125 option (<b>-S</b>) that can be used to increase the size of its stack. As long
126 as the stack is large enough, another option (<b>-M</b>) can be used to find the
132 Changing stack size in Unix-like systems
135 In Unix-like environments, there is not often a problem with the stack unless
136 very long strings are involved, though the default limit on stack size varies
142 Unfortunately, the effect of running out of stack is often SIGSEGV, though
144 limit on stack size by code such as this:
156 Changing stack size in Mac OS X
160 is also possible to set a stack size when linking a program. There is a
161 discussion about stack sizes in Mac OS X at this web site:
