From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: php 7 upgrade -- segmentation fault
Date: Wed, 30 Nov 2016 01:08:00 -0000 [thread overview]
Message-ID: <d7efaf50-2846-7dc5-e660-a26904f4e44c@cygwin.com> (raw)
In-Reply-To: <5118c6cbe09f3ed17a791417295bd3dafb91@guerrillamail.com>
On 2016-11-29 12:22, 59yfvs+f4bkzvgzw@guerrillamail.com wrote:
> I can revert to php5 (insecure) and the problem is gone. I just performed
> a full rebase which did nothing for this problem. Are you saying that on a
> Windows 7 64 bit Home system with 32 bit cygwin you are not having any issues?
I was testing on Windows 10 Pro.
> I found a solution that is not really satisfying. If I go into Windows
> System Advanced Settings - Data Execution Prevention tab, and I explicitly
> add php.exe to the list of DEP exceptions, I no longer have errors with preg_match().
Ah, that explains it. PHP 7 uses pcre's JIT functionality where 5.6 did
not. I guess you'd have the same problem with anything using a JIT.
You will have to handle such issues with DEP on your end.
--
Yaakov
--
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
next prev parent reply other threads:[~2016-11-29 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 20:14 59yfvs+f4bkzvgzw
2016-11-30 1:08 ` Yaakov Selkowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-30 2:38 5a1dvi+28lxtut1an
2016-11-29 18:21 59yfvs+f4bkzvgzw
2016-11-29 18:25 ` Yaakov Selkowitz
2016-11-29 18:11 59yfvs+f4bkzvgzw
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=d7efaf50-2846-7dc5-e660-a26904f4e44c@cygwin.com \
--to=yselkowitz@cygwin.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).