From owner-freebsd-ports@FreeBSD.ORG Wed Sep 13 22:42:12 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08F4B16A412 for ; Wed, 13 Sep 2006 22:42:12 +0000 (UTC) (envelope-from eculp@bafirst.com) Received: from bafirst.com (72-12-2-214.wan.networktel.net [72.12.2.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F53343D46 for ; Wed, 13 Sep 2006 22:42:11 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from localhost (localhost [127.0.0.1]) (uid 80) by bafirst.com with local; Wed, 13 Sep 2006 17:42:10 -0500 id 00095805.45088942.000056AB Received: from dsl-189-129-2-76.prod-infinitum.com.mx (dsl-189-129-2-76.prod-infinitum.com.mx [189.129.2.76]) by mail.bafirst.com (Horde MIME library) with HTTP; Wed, 13 Sep 2006 17:42:10 -0500 Message-ID: <20060913174210.swpuv1b9cw0owc0w@mail.bafirst.com> Date: Wed, 13 Sep 2006 17:42:10 -0500 From: eculp@bafirst.com To: freebsd-ports@freebsd.org References: <4507C944.1040006@sympatico.ca> <20060913121637.GA67429@icarus.home.lan> <450866E4.3070507@sympatico.ca> In-Reply-To: <450866E4.3070507@sympatico.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.1-cvs Subject: Re: PHP 5.1.6 Command Line Arg Gives Seg Fault 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: Wed, 13 Sep 2006 22:42:12 -0000 Quoting Ron Tarrant : > Jeremy Chadwick wrote: >> >> Can you provide a gdb backtrace of this problem? It might give >> others, and yourself, a better idea of where the problem is. Use >> the following: `gdb --args php --version`, and after the sig11 at >> the (gdb) prompt, do "bt". >> >> >> > Hmmm.... I'm guessing this isn't possible, although I could be wrong. > If php is compiled with debug hooks, the error doesn't occur. If it's > compiled without, there's no debug stack. Perhaps that's why this > hasn't been solved yet? The exact same thing happened to me and I mentioned it in my email to the list. With dbug everything worked wonderfully. In fact I left it that way for a couple of weeks until I had time to try one of the machines like I mentioned previously. ed