When running pear/PHPDoc php.exe (built from current CVS) crashes on
Win32.
set mem_limit to high value ( 32MB), running PHPDoc over PEAR is a hardcore
test...
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Alexander Merz wrote:
set mem_limit to high value ( 32MB), running PHPDoc over PEAR is a
hardcore test...
Nevertheless, I would expect a PHP warning instead of a crash, no?
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
Did I help you?
On Fri, 02 Nov 2001, Sebastian Bergmann wrote:
Alexander Merz wrote:
set mem_limit to high value ( 32MB), running PHPDoc over PEAR is a
hardcore test...
Nevertheless, I would expect a PHP warning instead of a crash, no?
No. This is a limitation of the PCRE library, which manifests
Andrei Zmievski wrote:
No. This is a limitation of the PCRE library, which manifests itself
when you work with very long strings and fairly complex patterns.
Can't we catch this in our extension? Crashes are not nice :)
--
Sebastian Bergmann
http://sebastian-bergmann.de/
On Fri, 02 Nov 2001, Sebastian Bergmann wrote:
Andrei Zmievski wrote:
No. This is a limitation of the PCRE library, which manifests itself
when you work with very long strings and fairly complex patterns.
Can't we catch this in our extension? Crashes are not nice :)
It really depends
Andrei Zmievski wrote:
It really depends both on the string *and* the pattern used. Short of
doing setjmp/longjmp, I don't see a good way of dealing with it, and
even that is evil.
Additional note: PHPDoc did not crash, when I used it on the
phpOpenTracker source tree, which was about a
When running pear/PHPDoc php.exe (built from current CVS) crashes on
Win32.
The MSVC++ Debugger shows a stack overflow in ext/pcre/pcrelib/pcre.c
in
static BOOL
match(register const uschar *eptr, register const uschar *ecode,
int offset_top, match_data *md, unsigned long int
