Hi Florian! On Tue, 22 Apr 2008 22:45:40 +0200 Florian Weimer <[EMAIL PROTECTED]> wrote:
> > Default recursion limit assumed by pcre seems to be set way too > > high. Rebuilding pcre with --with-match-limit-recursion set to > > lower value avoids SEGVs. > > Ah, I wasn't ware of that option, thanks. Hopefully it's not > necessary to specify --disable-stack-for-recursion. That actually may not be a very good advice after all, as was pointed to my by Fedora pcre maintainer. Setting some low fixed recursion limit may cause problems to users that faced this problem and addressed it by increasing process stack size (either via ulimit or setrlimit). Also note that pcrestack(3) already documents this problem quite well. Besides that ~500 byte suggestion, which seems too small for the systems I tested on. Sorry, I've missed that man page before. > There's also a konqueror/KDE Javascript bug report related to this, I > think. Yes, that's very likely, as KDE uses pcre to for JavaScript regular expressions. > We should test this flag in unstable for a while, and if it works, > apply it to a stable update. As mentioned above, can cause regression for some users. Probably trying to provide match_limit_recursion during pcre_exec call may be a better start, with some ( ( 'ulimit -s' - stack_used_by_konqueror ) / 500) - some_constant ) guesswork. -- Tomas Hoger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
