Date: Mon, 17 Nov 2003 09:47:28 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: vze2ztys@verizon.net Cc: current@freebsd.org Subject: Re: kldload(2) and debug kernels Message-ID: <20031117094635.O21453@carver.gumbysoft.com> In-Reply-To: <20031116071046.HNIV1420.out003.verizon.net@outgoing.verizon.net> References: <20031116071046.HNIV1420.out003.verizon.net@outgoing.verizon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 16 Nov 2003 vze2ztys@verizon.net wrote: > 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. If you give a specific path to a module then it will load that module. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031117094635.O21453>