From: "Ing. Viliam Kubis" <viliam.kubis@gmail.com>
To: cygwin@cygwin.com
Subject: PHP 7.1.12 still crashes on cygwin when parsing files that are multiple of 4096 bytes in size
Date: Sun, 07 Jan 2018 15:48:00 -0000 [thread overview]
Message-ID: <b483848d-91eb-1dd3-2d57-457496a6afa7@gmail.com> (raw)
Hello,
I have been using cygwin as my local PHP development suite, and for some
time now, PHP has been crashing on files that are a multiple of 4k in
size. Just run this in your terminal to observe the crash:
kbs1@DESKTOP-QR0EO0L /cygdrive/c/Users/kbs1/Desktop
$ if [ -f test.php ]; then rm test.php; fi; for i in `seq 4096`; do echo
-n ' ' >> test.php; done; php -v; php test.php; rm test.php
PHP 7.1.12 (cli) (built: Dec 7 2017 02:53:41) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.1.0, Copyright (c) 1998-2017 Zend Technologies
with Zend OPcache v7.1.12, Copyright (c) 1999-2017, by Zend Technologies
Segmentation fault (core dumped)
php.exe.stackdump will be left behind.
For some time, a proper patch is posted here:
https://cygwin.com/ml/cygwin/2017-05/msg00350.html
But I really don't want to recompile PHP every time I run setup.exe and
PHP updates, when will the patch be adopted in the cygport it self
please? Or are we waiting for something else, is the patch improper or
similar?
Thank you,
Ing. Viliam Kubis
--
Sent using SeaMonkey mail
--
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:[~2018-01-07 15:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b483848d-91eb-1dd3-2d57-457496a6afa7@gmail.com \
--to=viliam.kubis@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).