From owner-freebsd-advocacy Sun May 30 15:30:10 1999 Delivered-To: freebsd-advocacy@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 38C0F150C3 for ; Sun, 30 May 1999 15:30:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id PAA93406; Sun, 30 May 1999 15:30:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: by hub.freebsd.org (Postfix, from userid 32767) id B817E14E7B; Sun, 30 May 1999 13:16:54 -0700 (PDT) Message-Id: <19990530201654.B817E14E7B@hub.freebsd.org> Date: Sun, 30 May 1999 13:16:54 -0700 (PDT) From: aron@cs.rice.edu To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: advocacy/11947: kldload doesn't produce a linked file for the module Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Number: 11947 >Category: advocacy >Synopsis: kldload doesn't produce a linked file for the module >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-advocacy >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun May 30 15:30:01 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Mohit Aron >Release: FreeBSD-3.2-Release >Organization: Rice University >Environment: FreeBSD luzern.cs.rice.edu 3.2-RELEASE FreeBSD 3.2-RELEASE #2: Fri May 28 15:22:48 CDT 1999 aron@luzern.cs.rice.edu:/usr/src/sys/compile/LUZERN i386 >Description: The modload command in the earlier lkm interface used to produce a linker file as a result of the '-o' option. This file used to give the actual addresses of variables in the module after loading it. This information was very useful as then the values of variables in the module can be read by reading /dev/kmem. Unfortunately, kldload doesn't produce any such file. Can a similar option be added to kldload so that it too starts producing this linker file. Addresses of variables in the module can be obtained by adding the address where the module is loaded (reported by kldstat) to the address of the variable in the module (before relocation). However, this is a cumbersome way and it'll much more convenient to have a linker file that gives all this information. >How-To-Repeat: Load a kld module with kldload and notice that no linker file is produced. Load an lkm module with modload and a linker file is put in /tmp (unless a '-o' option is given). >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message