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

It's more serious than I thought as ANY use of preg_match causes the
segfaulting, even in interactive mode.

$ php -a
Interactive shell

php > $msg="!Hello"; if ( preg_match('#^!Hello\b#', $msg) ) echo "wee";
Segmentation fault (core dumped)

php > if ( preg_match('/d/', 'dba') ) echo "wee";
Segmentation fault (core dumped)





----
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 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 18:22 59yfvs+f4bkzvgzw [this message]
2016-11-29 18:56 ` Yaakov Selkowitz

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=39cb390b31a1668c6b3f41bf535bc80c0889@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).