public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: <59yfvs+f4bkzvgzw@guerrillamail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: php 7 upgrade -- segmentation fault
Date: Tue, 29 Nov 2016 18:11:00 -0000	[thread overview]
Message-ID: <10e5f349bf47dcecbf59419085da3615494@guerrillamail.com> (raw)

I just updated from php5.6.27-1 to php7.0.13-1 .  A previously working script now segfaults and the stackdump isn't terribly helpful in tracing the issue:

$ cat php.exe.stackdump
Exception: STATUS_ACCESS_VIOLATION at eip=FFBC0008
eax=80155DA0 ebx=80165AC8 ecx=00289080 edx=00000004 esi=FFBC0008 edi=80165598
ebp=00000004 esp=0028905C program=D:\cygwin\bin\php.exe, pid 8504, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame     Function  Args

The script in question creates a persistent SSL socket to a server (not http), sets socket blocking to false, then enters into a while loop to process messages and respond.  I can tell that it is able to establish the connection.  The segmentation fault is happening somewhere in the loop.

NOW REMEMBER, this script has been working fine for months under the old php5.x branch.  Only with this change to php7 am I getting segfaults.  Also this script runs perfectly fine on a linux server using the same version of php7.

There is clearly a problem with this new php7 build for cygwin. I am happy to help gather more data on the issue if you direct me to the steps to undertake. It seems likely the problem revolves around the socket functions.

Some other details:
* 32 bit cygwin on a 64 bit Windows 7 machine
* php -v works
* php -a works
* basic php scripts work





----
Sent using Guerrillamail.com
Block or report abuse: https://www.guerrillamail.com/abuse/?a=QlhzEgQOY7cMjxm9%2FjAcfRk%3D



--
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-11-29 17:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 18:11 59yfvs+f4bkzvgzw [this message]
2016-11-29 18:21 59yfvs+f4bkzvgzw
2016-11-29 18:25 ` Yaakov Selkowitz
2016-11-29 20:14 59yfvs+f4bkzvgzw
2016-11-30  1:08 ` Yaakov Selkowitz
2016-11-30  2:38 5a1dvi+28lxtut1an

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=10e5f349bf47dcecbf59419085da3615494@guerrillamail.com \
    --to=59yfvs+f4bkzvgzw@guerrillamail.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).