From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 106478 invoked by alias); 18 May 2017 14:22:39 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 106465 invoked by uid 89); 18 May 2017 14:22:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,GIT_PATCH_2,RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=ham version=3.3.2 spammy=D*yandex.ru, UD:ini, UD:php.ini, phpini X-HELO: mail-qt0-f181.google.com Received: from mail-qt0-f181.google.com (HELO mail-qt0-f181.google.com) (209.85.216.181) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 18 May 2017 14:22:36 +0000 Received: by mail-qt0-f181.google.com with SMTP id v27so35240224qtg.2 for ; Thu, 18 May 2017 07:22:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=sQcwz6dlOmX3n34RMRTFIBgxHCMtrug0n8lBbps5GDE=; b=cg9VjfS40NGVwKSr74Go36B2UwWngYBA5qj7hCYPE98Rt9lIu+lloGc943c74iUUly /0wenwBNuK3/Y4+I+a35mknHRwT7PRs7oXUJq7ALixgiTkSzEQ2RPAKKfE+qEHpCoI/r ogusvYeT5qOUhOb85brj44bV1CWINjWqmhVGJg5DskM4SzuU2aPXVy6IQuLJ6Cppkrm5 uVZXhgoF4EpK4bMfE0pn+hp6wNlMxv9yMVfdFNKR2+VjTCB2lPFWfWXM2JYTVLCVtypm sl05rK0RXyoOUOZYy0sVSGbxrNCc8SwVzWDHtbn+k6h5N9WtH+XEhyT+VYSInsOqQPSh dw0g== X-Gm-Message-State: AODbwcABr0G6eQ7nsM5qtVeVOcY7QyAAq4rlql+uChh2NujLkmUYtQFe 32PXEcDH8XfqJ1UYQ1vF8x7XItjOqWufnsc= X-Received: by 10.237.33.183 with SMTP id l52mr3967609qtc.165.1495117357868; Thu, 18 May 2017 07:22:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.190.71 with HTTP; Thu, 18 May 2017 07:22:17 -0700 (PDT) In-Reply-To: <114969752.20170518153452@yandex.ru> References: <114969752.20170518153452@yandex.ru> From: Sky Diver Date: Thu, 18 May 2017 14:32:00 -0000 Message-ID: Subject: Re: Composer segfault on multiple configurations To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2017-05/txt/msg00300.txt.bz2 On Thu, May 18, 2017 at 3:34 PM, Andrey Repin wrote: > Please don't top-post, and don't quote raw email addresses. Fair enough. On Thu, May 18, 2017 at 3:59 PM, Richard H Lee wrote: > On 18/05/2017 13:34, Andrey Repin wrote: >> >> Try turning pcre.jit off, it was known to be a problem in the past. > > > This is already turned off in the cygport patches. I'm not sure if Richard is referring to a released version or a manually compiled one, but prior to posting my issue I already went over earlier discussions regarding pcre.jit. This is the configuration in my php.ini: pcre.jit=0 I assume this means it's off. On Thu, May 18, 2017 at 3:34 PM, Andrey Repin wrote: > Greetings, Sky Diver! > > Please don't top-post, and don't quote raw email addresses. > >> On Wed, May 17, 2017 at 11:24 PM, Richard H Lee wrote: >>> On 17/05/2017 20:17, Sky Diver wrote: >>>> >>>> Running "composer install" with the following composer.json ends up in >>>> a segmentation fault. >>>> >>>> ---------- START ----------- >>>> { >>>> "require": { >>>> "propel/propel": "~2.0@dev" >>>> }, >>>> "config": { >>>> "optimize-autoloader": true >>>> } >>>> } >>>> ---------- END ------------- >>>> >>>> (*) Note: when "optimize-autoloader" is set to false the error doesn't >>>> occur. >>> >>> I think this may be to do with the 4096 error bug. >>> >>> Composer will pull in the files and run them. One of them is: >>> vendor/propel/propel/src/Propel/Runtime/DataFetcher/PDODataFetcher.php >>> >>> From you project directory, try running: >>> php vendor/propel/propel/src/Propel/Runtime/DataFetcher/PDODataFetcher.php >>> >>> That probably will give you a segfault. I'm not sure if changing the >>> filesize will help, because composer probably will fetch a fresh copy of >>> the file. >>> >>> I did provide a small patch a few weeks ago. That might help. You'd need >>> to recompile and install php though cygports to use it. > >> Thanks Richard, you've hit the nail right on the head. >> Running PHP on that specific file does produce the segfault. > >> I'm currently running composer via "Bash on Ubuntu on Windows". I may >> compile PHP from cygports later but currently I need to make up for >> lost time at work over this. >> Any idea when your fix will get released as an official cygwin PHP package? > >> Thanks again. > > Try turning pcre.jit off, it was known to be a problem in the past. > > > -- > With best regards, > Andrey Repin > Thursday, May 18, 2017 15:31:02 > > Sorry for my terrible english... > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple