From owner-freebsd-ports@FreeBSD.ORG Tue Jun 28 18:38:33 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA5FE1065672 for ; Tue, 28 Jun 2011 18:38:33 +0000 (UTC) (envelope-from attos.janus@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8A0328FC08 for ; Tue, 28 Jun 2011 18:38:33 +0000 (UTC) Received: by yic13 with SMTP id 13so266962yic.13 for ; Tue, 28 Jun 2011 11:38:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6uZ3FyHMCu+/jEQjs4c2dFMMImlqjrlHUfXQ8ANLaOs=; b=SC4Hva+mlw8ZZCknjXaDkmo0MT2+K/TjihTEtr8qupPQOe/AoI0FfEgn2f35lgaVRG lBH5c3UwbXtycIks2FjDdcbD6exJcqekUMP4A2NDn+0fs8momhzqkvA6KceE9r10fgis pvzqJYSLd6Qez7v34B8ctIpNitZRCMYat0lEU= MIME-Version: 1.0 Received: by 10.101.196.7 with SMTP id y7mr5085340anp.154.1309286312802; Tue, 28 Jun 2011 11:38:32 -0700 (PDT) Received: by 10.100.31.2 with HTTP; Tue, 28 Jun 2011 11:38:32 -0700 (PDT) In-Reply-To: References: Date: Tue, 28 Jun 2011 14:38:32 -0400 Message-ID: From: Attos To: Eric Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-ports Subject: Re: SQLite 3 PHP extensions issues after upgrading to PHP5 5.3.6_1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 18:38:34 -0000 Done that. Appending and moving around sqlite3.so did not fix it. Just commenting it out did the trick. On Tue, Jun 28, 2011 at 1:45 PM, Eric wrote: > > From: Attos > > Hello, > > Just upgraded to php5-5.3.6_1 and the SQLITE 3 extensions > > (php5-pdo_sqlite-5.3.6_1 and php5-sqlite3-5.3.6_1) are causing PHP to > core > > dump. > > I commented them from /usr/local/etc/php/extensions.ini and the > segmentation > > faults disappear. > > I've always fount that re-ordering the entries in /usr/local/etc/php/ > extensions.ini through trial and error tends to make the problem go away > and > allows one to use the extension without the faults. > > Jim Pingle posted a script ages ago on his blog[1] to do some rough and > ready re-ordering, if you fancy giving that a try. > > Regards > > Eric > > [1] http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround > > > -- Attos Janus