From owner-freebsd-hackers Fri May 28 16:11:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id DA73914E8C for ; Fri, 28 May 1999 16:11:19 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id SAA04410 for freebsd-hackers@freebsd.org; Fri, 28 May 1999 18:11:19 -0500 (CDT) From: Mohit Aron Message-Id: <199905282311.SAA04410@cs.rice.edu> Subject: linked symbols using kldload To: freebsd-hackers@freebsd.org Date: Fri, 28 May 1999 18:11:18 -0500 (CDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm using FreeBSD-3.2 and am trying to upgrade to the kld interface from the old lkm interface for loadable kernel modules. kldload doesn't seem to produce a linker output file upon loading a module - modload used to do this on the other hand. I've found this output file extremely valuable for kernel debugging - I can read the addresses of variables in my module and then read/write the values from these addresses from /dev/kmem. Are there any plans to extend kldload to incorporate the same functionality ? - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message