Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:55818 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96880 invoked from network); 16 Oct 2011 18:32:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Oct 2011 18:32:03 -0000 X-Host-Fingerprint: 88.217.187.160 host-88-217-187-160.customer.m-online.net Received: from [88.217.187.160] ([88.217.187.160:25219] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FD/B2-07463-0032B9E4 for ; Sun, 16 Oct 2011 14:32:02 -0400 Message-ID: To: internals@lists.php.net Date: Sun, 16 Oct 2011 20:31:24 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 88.217.187.160 Subject: Issues with Traits / php crashes From: harald.lapp@gmail.com (Harald Lapp) hi, i wonder if anybody out there already tried traits in more complex php applications. i am currently trying to rewrite part of a somehow complex application to use traits and i have the problem, that my scripts are dying, as soon as i include the trait. with the current php-5.4 beta my processes are dying, but with the lates snapshot, not -- i still get the message: 2011-10-16 16:41:19: (mod_fastcgi.c.2462) unexpected end-of-file (perhaps the fastcgi process died): pid: 18556 socket: unix:/tmp/php-fastcgi.socket-3 2011-10-16 16:41:19: (mod_fastcgi.c.3254) response not received, request sent: 1329 on socket: unix:/tmp/php-fastcgi.socket-3 for /index.php , closing connection ... in my logs, though. the real problem now is that i seem to be unable to isolate the issue. it seems to have something to do with properties in traits, but if i try to reconstruct this with simple example scripts, there won't be any crash. my question is: is there anything i can do to track this problem down, to get a useful backtrace / core dump or any other information, that would count as useful information for filing a bug-report? as it is know, i have nothing in my hands besides the info, that it's crashing ... thanks in advance! harald