public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: PHP 7.0.14 crashing with minimal set of extensions
Date: Sun, 18 Dec 2016 19:47:00 -0000	[thread overview]
Message-ID: <c74f035f-09fe-3a7e-302a-eed7fdb0d922@SystematicSw.ab.ca> (raw)
In-Reply-To: <919263915.20161218214043@yandex.ru>

On 2016-12-18 11:40, Andrey Repin wrote:
> Greetings, Brian Inglis!
>> On 2016-12-14 04:04, Andrey Repin wrote:
>>> Greetings, Yaakov Selkowitz!
>>>> On 2016-12-13 12:06, Andrey Repin wrote:
>>>>> Here's strace and stackdump from latest crash with Cygwin 
>>>>> 2.6.1-2 project.rootdir.org/.offload/crash-php-7.14.tar.xz
>>>> Are you 100% sure that your code is compatible with PHP 7?
>>>> The only segfaults I have seen so far is with old code.
>>> It's Composer. It runs with native PHP7 of the same version just
>>> fine.
>> Possibly JIT/DEP conflict see 
>> https://cygwin.com/ml/cygwin/2016-11/msg00336.html
> Gah… confirmed. Setting pcre.jit = Off let it run.

Does the native app use JIT and have no problems with Windows DEP?
Does PHP need some Cygwin specific patches to re-mmap JIT code as rx, 
or Cygwin patches so Windows sees mmap rx regions as executable code, 
or otherwise "blesses" JIT code so it is not crashed by DEP?
There should at least be some way to indicate there is a DEP issue 
rather than just crashing with a segv!

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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:[~2016-12-18 19:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13 18:20 Andrey Repin
2016-12-13 19:07 ` Brian Inglis
2016-12-13 21:50   ` Andrey Repin
2016-12-13 22:23     ` Brian Inglis
2016-12-14  7:35 ` Yaakov Selkowitz
2016-12-14 14:25   ` cyg Simple
2016-12-14 17:20   ` Andrey Repin
2016-12-17  7:30     ` Brian Inglis
2016-12-18 18:51       ` Andrey Repin
2016-12-18 19:47         ` Brian Inglis [this message]
2016-12-19 20:21           ` Andrey Repin

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=c74f035f-09fe-3a7e-302a-eed7fdb0d922@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).