From owner-freebsd-questions@FreeBSD.ORG Fri May 2 14:58:40 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0042F1065671 for ; Fri, 2 May 2008 14:58:39 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from mail.potentialtech.com (internet.potentialtech.com [66.167.251.6]) by mx1.freebsd.org (Postfix) with ESMTP id CB6128FC25 for ; Fri, 2 May 2008 14:58:39 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from vanquish.ws.pitbpa0.priv.collaborativefusion.com (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.potentialtech.com (Postfix) with ESMTPSA id 4DDAAEBC3B; Fri, 2 May 2008 10:58:38 -0400 (EDT) Date: Fri, 2 May 2008 10:58:53 -0400 From: Bill Moran To: Chris Maness Message-Id: <20080502105853.36874cdf.wmoran@potentialtech.com> In-Reply-To: References: X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD List Subject: Re: Compiling in Debugging Flags X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2008 14:58:40 -0000 In response to Chris Maness : > How do I compile in debugging into apache using ports? There is no > configmenu when one begins to install/compile the port. I'm still having > trouble with apache crashing on a recently upgraded server. (after I have > rebuilt all of the ports). I was having the same problem with apache on a > sandbox server after upgrade to 7.0-RELEASE. I wasn't ever able to figure > it out. I have just upgraded apache on a production server, and I am not > able to cut over until apache working. I get no errors in log files no > errors on std out, and no core dump either. If I attache to GDB, I get no > messages either. Wierd. First, put WITH_DEBUG=absolutely in /etc/make.conf. This will cause all ports that are built to have debug symbols. I believe you need to save the /usr/ports/*/[portname]/work directory after installing, so don't do a make clean until you've archived that somewhere. Then, ensure the sysctls in the kernel are all frobbed to allow coredumps. Specifically: kern.coredump: 1 kern.sugid_coredump: 1 Then, make sure the www user has write access to wherever it's trying to dump to. Personally, I prefer to tweak kern.corefile to be /usr/local/corefiles/%N.%P.core. I can then ensure that directory exists and that all users have write access to it (probably not the best idea on a production server, however) >From there, you should be getting usable coredumps. -- Bill Moran http://www.potentialtech.com