ID: 36983 Updated by: [EMAIL PROTECTED] Reported By: crisp at tweakers dot net Status: Assigned Bug Type: PCRE related Operating System: all PHP Version: 4.4.2 Assigned To: andrei New Comment:
There you go, you turned it into a non-bogus bug report we can actually do something about. Previous Comments: ------------------------------------------------------------------------ [2006-04-05 23:01:05] crisp at tweakers dot net Just a small update on this. PCRE is actually issuing an error; specifically PCRE_ERROR_MATCHLIMIT (-8) Apparently when PCRE goes into backtracking it will try any combination of the OR'ed subpattern resulting into over 10.000.000 calls to match(). Obviously there is no construction that first checks if (and where) a possible alternative defined as an OR can match within the part that is being backtracked. So this seems to be defined behaviour of PCRE (but it could use improvement if even a simple case like the one I constructed already triggers this behaviour), but my question now is why does PHP not raise a warning or error when PCRE exits with one? ------------------------------------------------------------------------ [2006-04-05 20:26:55] [EMAIL PROTECTED] >bogus' has a negative ring to it - at least it does for >me as a non-native English-speaking person. Well, it doesn't have a negative meaning for me, although I'm not a native speaker either =) ------------------------------------------------------------------------ [2006-04-05 20:22:19] crisp at tweakers dot net That last remark is taking my well-meant criticism to the extreme; surely you will know that that was not what I meant. 'bogus' has a negative ring to it - at least it does for me as a non-native English-speaking person. Anyway, let's leave it at that; I'll submit this to the PCRE developers. ------------------------------------------------------------------------ [2006-04-05 20:00:31] [EMAIL PROTECTED] "Bogus" doesn't mean "reporter is an idiot, the bug exists only in his imagination". "Bogus" quite often means "there were no issue we can fix, so we can't CLOSE it (i.e. FIX), we can only mark it as BOGUS (i.e. not PHP problem)". Status "CLOSED" means there was a bug in PHP itself and it was fixed. This is not the case. Nothing personal whatsoever. PCRE category exists for quite obvious reason: PHP functions in ext/pcre may be buggy, so you should be able to report problems in this category. Yes, we could of course add some more statuses like "not PHP problem", "RTFM", "floats have limited precision" or "please copy libmysql.dll to $PATH", but well.. does it make any sense? Not to me. ------------------------------------------------------------------------ [2006-04-05 19:52:12] crisp at tweakers dot net Not to be disrespectfull but honestly I feel a bit put off by the reply I'm getting here. When I personally put time in creating a valid and easy to follow testcase and submit it here, believing this is the right place to go (I found this bug using a PHP built-in function and it is PCRE related - why else do you have that category?) and by doing so helping in improving PHP, and all I'm getting is a 'this bug is bogus'-reply when it formally isn't. Maybe you should consider some more status codes like '3rd party related' or so - at least something that doesn't have such a negative sound and that actually reflects the status of the bugreport. And even when such an issue is 3rd party related I would think the PHP development team should at least feel some responsibility or show some concern about such issues. You probably have better contacts with these parties than I do and it is in your benefit too that such issues get resolved. Thank you in advance for making me think twice about submitting a bug the next time I encounter one; it'll probably save me some time... ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/36983 -- Edit this bug report at http://bugs.php.net/?id=36983&edit=1