From owner-freebsd-current@FreeBSD.ORG Wed Apr 14 08:33:30 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CC75106566B for ; Wed, 14 Apr 2010 08:33:30 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: from mail-iw0-f171.google.com (mail-iw0-f171.google.com [209.85.223.171]) by mx1.freebsd.org (Postfix) with ESMTP id 583AF8FC17 for ; Wed, 14 Apr 2010 08:33:30 +0000 (UTC) Received: by iwn1 with SMTP id 1so3177447iwn.27 for ; Wed, 14 Apr 2010 01:33:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:received:message-id :subject:from:to:content-type; bh=Me6QaI0ENFKs3ml71MM7vaK0cLJmUFtiO+JRX51WGSo=; b=lol5hiFRC+mYn5s8KeNgYU/EF3ZmFaavAXe9DKJX3CU0VbLW5NHkvJXUHqtf9wTp1m uLKqcy/8xzIa5px9KY3gyaPwtk9op7OmHPPb1Zo07V4acjIEeBwhrfmi5AU93zYqoQRI BU+Ur6T5/iNKhlA9B5r+cYGNRJ9qRbjjk/rNQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=N58tDlCw6jCunGW6BE1V9PBwJJVaQiN9bJx5OVMNl3xrRdWuEVththxpXHyzExnsCB mdxvZfB52PUMIWeETZPuttkDh5CDSuz2WU+MDHX0S7b/GNS5HB8vlvjQdiwwCUXK8wZa HGvsH/0i1ktAcLv7nB6sN6qosaSRkglvrFL8Y= MIME-Version: 1.0 Received: by 10.231.213.16 with HTTP; Wed, 14 Apr 2010 01:33:29 -0700 (PDT) Date: Wed, 14 Apr 2010 01:33:29 -0700 Received: by 10.231.144.197 with SMTP id a5mr3196587ibv.5.1271234009813; Wed, 14 Apr 2010 01:33:29 -0700 (PDT) Message-ID: From: Navdeep Parhar To: netchild@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Does "makeoptions WITH_CTF=yes" actually work? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Apr 2010 08:33:30 -0000 I read the UPDATING entry that accompanied r206082 and added WITH_CTF=yes to my kernel config, hoping to get CTF information in the kernel and all modules. No luck. It appears that NO_CTF remains set to 1 inspite of the undef NO_CTF in various .mk files and ctfconvert never runs. Can anyone confirm whether r206082 works as advertised or not? This is the diff between my config and amd64/conf/GENERIC: 24a25 > makeoptions WITH_CTF=yes 66,67c67,68 < #options KDTRACE_FRAME # Ensure frames are compiled in < #options KDTRACE_HOOKS # Kernel DTrace hooks --- > options KDTRACE_FRAME # Ensure frames are compiled in > options KDTRACE_HOOKS # Kernel DTrace hooks 72a74 > options DDB_CTF This is /etc/make.conf on my system: CPUTYPE?=core2 DEBUG_FLAGS=-g -fno-inline-functions -fno-inline-functions-called-once I built the kernel with a "make -j16 buildkernel" in /usr/src. Regards, Navdeep