From owner-freebsd-ports@FreeBSD.ORG Tue Jul 20 21:26:11 2010 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F40F106573B for ; Tue, 20 Jul 2010 21:26:11 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 198A78FC16 for ; Tue, 20 Jul 2010 21:26:10 +0000 (UTC) Received: from eagle.syrec.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id o6KLQ85P028193; Tue, 20 Jul 2010 14:26:08 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <4C461470.4040407@rawbw.com> Date: Tue, 20 Jul 2010 14:26:08 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.10) Gecko/20100708 Thunderbird/3.0.5 MIME-Version: 1.0 To: Remko Lodder References: <4C4416A7.3060308@rawbw.com> <4C45E262.40702@rawbw.com> <2BF3C2F7-314C-432A-86E6-D743E5FBF983@elvandar.org> <4C46013F.1080301@rawbw.com> <5EECDB8B-326A-4A88-8E10-C0A6DEAF6937@elvandar.org> In-Reply-To: <5EECDB8B-326A-4A88-8E10-C0A6DEAF6937@elvandar.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org Subject: Re: Wordpress outputs an empty page after ports upgrade 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, 20 Jul 2010 21:26:11 -0000 On 07/20/2010 13:12, Remko Lodder wrote: > Wordpress has the option to enable debugging, can you please try that? My website (see my signature) is running on 8-STABLE, without issues, version from thursday or something so fairly > recent. > > Thanks, > Remko > > (p.s. does httpd mention any BUS errors or SEGFAULTS?) > > Remko, No, no BUS or SEGFAULT. My quick debugging didn't produce much results. This must be some robustness issue. It looks most likely like an issue in WP itself. So I filed the PR: http://core.trac.wordpress.org/ticket/14367 Thanks, Yuri