At Fri, 27 Jun 2014 20:44:20 +0200, Ondřej Surý wrote: > However I would suggest to report this bug to upstream developers > at bugs.php.net. I could cut&paste your bugreport into their interface, > but it would be better if you could be in touch with upstream directly, > since you can provide more details if asked.
To get a proper bugreport I did take a snapshot from snaps.php.net and compiled it with these flags: './configure' '--with-pgsql' '--with-gd' '--with-curl' '--with-openssl' '--enable-phar' '--enable-cli' '--with-iconv' '--with-zlib' '--with-mhash' '--enable-sockets' '--with-mcrypt' '--enable-calendar' '--enable-mbstring' '--with-pdo-pgsql' '--enable-zip' '--enable-fpm' I then started the server this way: ~/tmp/php5.6-201406280430/sapi/cli/php -d date.timezone=Europe/Berlin app/console server:run Then ran the curl command and I got a proper exception from php/symfony but no mysterious crash with general protection. I then tried the same with 5.6 RC1 and got the same results. So I think this is somehow a debian issue :/. greetings Tim -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
