public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Sky Diver <skydivergm@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Composer segfault on multiple configurations
Date: Thu, 18 May 2017 11:02:00 -0000	[thread overview]
Message-ID: <CADWQZEtXVU5GMitWn1qFqSrXYE4D5LtSBOSWsayv=suGBR0aBQ@mail.gmail.com> (raw)
In-Reply-To: <d79e573f-5776-ed8e-da7e-667d04c54c7d@gmail.com>

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.

On Wed, May 17, 2017 at 11:24 PM, Richard H Lee
<ricardohenrylee@gmail.com> 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.
>
> --
> 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
>

--
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

  reply	other threads:[~2017-05-18  7:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17 19:32 Sky Diver
2017-05-17 20:47 ` Richard H Lee
2017-05-18 11:02   ` Sky Diver [this message]
2017-05-18 12:35     ` Andrey Repin
2017-05-18 13:33       ` Richard H Lee
2017-05-18 14:32       ` Sky Diver
2017-05-19 19:26     ` [ATTN: Yaakov Selkowitz / PHP maintainer] " Richard H Lee
2017-05-30 18:59       ` Richard H Lee
2017-05-30 20:47         ` Vince Rice
2017-05-31  1:02           ` Vince Rice
2017-05-22 19:54     ` Richard H Lee
2017-05-25  7:56       ` Sky Diver
2017-05-25 21:21         ` Memcache/d (Orig: Re: Composer segfault on multiple configurations) Richard H Lee
2017-05-27 10:51           ` Sky Diver

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADWQZEtXVU5GMitWn1qFqSrXYE4D5LtSBOSWsayv=suGBR0aBQ@mail.gmail.com' \
    --to=skydivergm@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).