From owner-freebsd-ports@FreeBSD.ORG Wed May 2 17:01:15 2007 Return-Path: X-Original-To: ports@FreeBSD.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B15CF16A402; Wed, 2 May 2007 17:01:15 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.freebsd.org (Postfix) with ESMTP id 84A9713C44B; Wed, 2 May 2007 17:01:15 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 9FBE15C5A; Wed, 2 May 2007 12:32:57 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KsWOKYGzNLKo; Wed, 2 May 2007 12:32:52 -0400 (EDT) Received: from [192.168.1.3] (pool-96-224-43-99.nycmny.east.verizon.net [96.224.43.99]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 5DB695C33; Wed, 2 May 2007 12:32:52 -0400 (EDT) Message-ID: <4638BD32.9040903@mac.com> Date: Wed, 02 May 2007 12:32:50 -0400 From: Chuck Swiger User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Alexander Nedotsukov References: <786602c60705020154k74b23dbkae585bf01a867f92@mail.gmail.com> <46385BB2.8040302@FreeBSD.org> In-Reply-To: <46385BB2.8040302@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, Thomas Zander Subject: Re: Undefine WITH_DEBUG? 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, 02 May 2007 17:01:15 -0000 Alexander Nedotsukov wrote: > Thomas Zander wrote: [ ... ] >> Is there an elegant solution to circumvent this and undefine WITH_DEBUG? > I think you need to add DEBUG_FLAGS="-g -O2 -fomit-frame-pointer". On some platforms, you'll need to get rid of -fomit-frame-pointer to have usable stack frames in the output executable for the debugger to use. Depending on the code and the bug in question, it might be easier to see what's going on using only "-g" or "-g -O"... -- -Chuck