Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:87261 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60513 invoked from network); 24 Jul 2015 07:34:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jul 2015 07:34:18 -0000 Authentication-Results: pb1.pair.com header.from=adam@adamharvey.name; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=adam@adamharvey.name; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.217.178 as permitted sender) X-PHP-List-Original-Sender: adam@adamharvey.name X-Host-Fingerprint: 209.85.217.178 mail-lb0-f178.google.com Received: from [209.85.217.178] ([209.85.217.178:33596] helo=mail-lb0-f178.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D8/60-57278-97AE1B55 for ; Fri, 24 Jul 2015 03:34:18 -0400 Received: by lbbyj8 with SMTP id yj8so9758278lbb.0 for ; Fri, 24 Jul 2015 00:34:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adamharvey.name; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=FYl22a7aIT5DYYbMPAllUlpc8yzdZDBrhPd7B1Vutmk=; b=I455oo/HrgPIZtBSyod+26REGWBXCuvUse57IMlSOBM6JjHhqrwimhqg3/7zQ94bmy Gt/xoAN4cN2Jktrg1AfP/atX6QmWmISgk3M5bcHSYa7QimZZ75NqeeMFU5liw2DewQ+s mDBrTCpRPYJQOWib/9huL4MK4LLz6v2UIBj7Y= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=FYl22a7aIT5DYYbMPAllUlpc8yzdZDBrhPd7B1Vutmk=; b=fo75W9nYrDx4lGcHnU8aKa76Svg3iwPDVkCwqvFIanwSx9xtrGDEyDocPimck7bGhJ 0F0qDHYJcm2DIeRqQIGDqBbVSrVUInlyXFl5z8Vic2ZTB5T/Cczuw8IQTQIlXVaPk9sa tT2B0qtytluGkg/Ma/yL6zrBIESetuxxKpucRIFbFdtUUpEr4a6f9esYO02yGAdQT6er I6dc34NuO/BfQNV7yIgxV/r2RTc6bWkScgbm7JL7OZ0DBbbEjuoQ/q05mTk0NoxWaYxf F5TQQuaZmOCinw/nTeuq+wO4jR9veAcz+gOChKM5OhcP5QyMy5wTUuZqxb1QpoLZh9pf emqQ== X-Gm-Message-State: ALoCoQlujle02D1cnEpR08bcMb56xGHb4A9Znxor3Sihrn+VBDQKRlBwB2HxqtQa2Cl82PCg2QP3 X-Received: by 10.112.124.164 with SMTP id mj4mr12155734lbb.3.1437723254001; Fri, 24 Jul 2015 00:34:14 -0700 (PDT) MIME-Version: 1.0 Sender: adam@adamharvey.name Received: by 10.25.159.70 with HTTP; Fri, 24 Jul 2015 00:33:54 -0700 (PDT) In-Reply-To: <55B136BE.8010006@gmx.de> References: <55B0CADD.8000807@gmx.de> <55B136BE.8010006@gmx.de> Date: Fri, 24 Jul 2015 00:33:54 -0700 X-Google-Sender-Auth: wOwwKNi40qw5OeSrZJXDO8NGKK8 Message-ID: To: Christoph Becker Cc: PHP internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] PCRE JIT stack size limit From: aharvey@php.net (Adam Harvey) On 23 July 2015 at 11:47, Christoph Becker wrote: > Therefore I tend to prefer a new ini setting (say, pcre.jitstack_limit). > That would mean, however, to add yet another ini setting, of which > there are already so many. I'm not a big fan of that, although it's at least in the spirit of what configuration settings are meant to be used for. What if we added the PCRE_ERROR_JIT_STACKLIMIT error constant to those exposed to userland so that it's more easily noticed via preg_last_error(), and adding a modifier that can be used to disable the JIT on a per-pattern basis (by setting PCRE_NO_START_OPTIMIZE, which admittedly disables other stuff too, but at least the regex will run)? At least then users could check the error when the regex fails and re-run the regex without the JIT if they chose to. How likely is the average user to hit this, do you think? Adam