From: Andrey Repin <anrdaemon@yandex.ru>
To: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>, cygwin@cygwin.com
Subject: Re: PHP 7.0.14 crashing with minimal set of extensions
Date: Mon, 19 Dec 2016 20:21:00 -0000 [thread overview]
Message-ID: <1092116748.20161219231726@yandex.ru> (raw)
In-Reply-To: <c74f035f-09fe-3a7e-302a-eed7fdb0d922@SystematicSw.ab.ca>
Greetings, Brian Inglis!
> 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?
pcre.jit => 1 => 1
Seems like "yes".
> 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?
That, I do not know.
> There should at least be some way to indicate there is a DEP issue
> rather than just crashing with a segv!
I do not enforce DEP here.
But I just found references that this can be a stack overflow issue.
--
With best regards,
Andrey Repin
Monday, December 19, 2016 23:12:14
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
prev parent reply other threads:[~2016-12-19 20:21 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
2016-12-19 20:21 ` Andrey Repin [this message]
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=1092116748.20161219231726@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=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).