From owner-freebsd-bugs  Wed Mar 13 09:46:35 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA12474
          for bugs-outgoing; Wed, 13 Mar 1996 09:46:35 -0800 (PST)
Received: from mailhost.Ipsilon.COM (foo-5-10.Ipsilon.COM [205.226.5.12])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA12468
          for <bugs@FreeBSD.org>; Wed, 13 Mar 1996 09:46:33 -0800 (PST)
Received: from ns.ipsilon.com (cell.Ipsilon.COM [205.226.1.190]) by mailhost.Ipsilon.COM (8.6.11/8.6.10) with SMTP id JAA27894 for <bugs@FreeBSD.org>; Wed, 13 Mar 1996 09:45:48 -0800
Date: Wed, 13 Mar 1996 09:45:48 -0800
Message-Id: <199603131745.JAA27894@mailhost.Ipsilon.COM>
X-Sender: chen@mailhost
X-Mailer: Windows Eudora Pro Version 2.1.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: bugs@FreeBSD.org
From: Jerry Chen <chen@ipsilon.com>
Subject: fyi: the symbol tabel of a loadable driver is not loaded
Sender: owner-bugs@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>> In FreeBSD 2.0.5, modload does not load the symbol table
>> into the kernel.
>
>Even if it would: it were of no use for you.  Since the driver is
>loaded to a dynamic location, the symbol table as created by ld(1)
>won't match the reality.

It seems to me that modload in FreeBSD is similar to the
one in SunOS 4.X.  How does SunOS 4.X work?  When I use
the kadb is SunOS 4.X, it shows the right symbol for a
loadable driver.

In fact, an engineer in my company already modified modload and
lkm in FreeBSD 2.0.5.  lkm calls X_db_sym_init() to notify ddb
where the symbol table is.  This sort of works.  But it is not
stable.  That is why we would like to see experts in FreeBSD to
engineer a fix to this problem.  If you want to get our code as
a starting point, we may be able to send it to you (if the
management approves).

Jerry