From owner-freebsd-current@FreeBSD.ORG Sat Nov 15 23:10:47 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9ADC616A4CE for ; Sat, 15 Nov 2003 23:10:47 -0800 (PST) Received: from out003.verizon.net (out003pub.verizon.net [206.46.170.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id A20BC43FBF for ; Sat, 15 Nov 2003 23:10:46 -0800 (PST) (envelope-from vze2ztys@verizon.net) Received: from outgoing.verizon.net ([192.168.1.6]) by out003.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20031116071046.HNIV1420.out003.verizon.net@outgoing.verizon.net> for ; Sun, 16 Nov 2003 01:10:46 -0600 X-Mailer: Openwave WebEngine, version 2.8.10 (webedge20-101-190-20021211) From: To: Date: Sun, 16 Nov 2003 1:10:46 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out003.verizon.net from [192.168.1.6] at Sun, 16 Nov 2003 01:10:46 -0600 Message-Id: <20031116071046.HNIV1420.out003.verizon.net@outgoing.verizon.net> Subject: kldload(2) and debug kernels X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Sun, 16 Nov 2003 07:10:47 -0000 It looks like the kldload system call takes the name of the module you give it, like "ums", and just tacks on ".ko" and searches in whatever the default paths are for kernel modules until it finds ums.ko. Peachy. But what about if you built your kernel and modules with debugging symbols added in? When you install the new kernel, all the files have ".debug" tacked on to the end. This seems to kill autoloading. The most recent change to moused makes it incompatible with ums.ko.debug, too. So I'm wondering if it would improve/break things to make it so that kldload() and its companions first look for "module.ko.debug" by default and then look for "module.ko" after that before giving up and returning an error. The advantage would be that you wouldn't have to muck about with loader.conf or extra boot scripts if you needed to work with a debug kernel. Thoughts? Andrew Lankford