Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:70560 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52456 invoked from network); 9 Dec 2013 17:45:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Dec 2013 17:45:02 -0000 Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.51 as permitted sender) X-PHP-List-Original-Sender: mike.php.net@gmail.com X-Host-Fingerprint: 74.125.83.51 mail-ee0-f51.google.com Received: from [74.125.83.51] ([74.125.83.51:46492] helo=mail-ee0-f51.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9B/72-40251-C9106A25 for ; Mon, 09 Dec 2013 12:45:01 -0500 Received: by mail-ee0-f51.google.com with SMTP id b15so1731226eek.38 for ; Mon, 09 Dec 2013 09:44:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:to:cc:date:in-reply-to:references :content-type:mime-version:content-transfer-encoding; bh=AIhvjPtAAOwyumuRCTYykepnFGxwH6gUb9DP539Z8QE=; b=h/Xh9ZPGSimkcTSchiRl07OKDD1J0suoJNDiLIfVnmeOOBCPW2bPOwoDmZS3opmto8 yy3moyJuYU/nRwdqJeBEszbS8gy1RsOicMPFQvL3VEG75uOUhr8o5knbDGe4Tv7bsafY BoSUeoGmHUzmSzE30nhYpuIC8r/VgF8a/tKTI3uk9aM4DNqlx+3Oz4z4TYQq0ZHqWDx5 6bEE5sOyA6eXN6ey/QbgZesQNWfULPF6aDU54HtjfDypatCAwie/fesYl2KKyX8hkvnn eVMMYYgy6IXwdlgXL2CwsqcquAIZYUS0uGKvnDzpE2dhxSzz0QaDe+7rZQQtwRvU/yFl Yz4Q== X-Received: by 10.15.54.130 with SMTP id t2mr13897621eew.72.1386611097567; Mon, 09 Dec 2013 09:44:57 -0800 (PST) Received: from [192.168.1.120] (178-18-170-101.customer.bnet.at. [178.18.170.101]) by mx.google.com with ESMTPSA id z42sm31320481eeo.17.2013.12.09.09.44.56 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 09 Dec 2013 09:44:56 -0800 (PST) Message-ID: <1386611095.9685.15.camel@smugmug> To: Ralph Schindler , Nikita Popov , Dmitry Stogov Cc: internals Date: Mon, 09 Dec 2013 18:44:55 +0100 In-Reply-To: <52A5FD1B.2020301@ralphschindler.com> References: <52A5FD1B.2020301@ralphschindler.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] SegFault 11 on 5.5.6 on function return From: mike.php.net@gmail.com (Mike) On Mon, 2013-12-09 at 11:25 -0600, Ralph Schindler wrote: > Hi all, > > We started noticing Segfaults in Travis when PHP was upgraded to 5.5.6. > I've tested this particular issue on both linux and mac and can > produce the segfault in both place. > > Looking at the backtrace (provided), can anyone offer assistance as to > what changed between 5.5.5 and 5.5.6 that might be causing this? > > I've been able to isolate the last line of PHP code that executes before > the segfault: > > > https://github.com/sebastianbergmann/phpunit/blob/3.7/PHPUnit/Util/Type.php#L203 > > I know the value of $value there to be null when this SegFault occurs. > > Also, the backtrace seems to hint at a problem in the garbage collector > since the source of the issue emanates from gc_remove_from_buffer(). > > My guesses... > > Is it possible that either the garbage collector is running and > destroying the stack, and that when unwinding the stack frames it is in > an inconsistent state and/or the return value for that particular > function is not placed on the stack so that the stack is in the proper > context when the return is processed? > > I can do additional research if anyone would like to point me in the > right direction, or I can provide access to a VM where this particular > backtrace was produced from. > > Thanks in advance. > -ralph RETVAL_ZVAL_FAST comes to mind.... Nikita, Dmitry? -- Regards, Mike