Re: kldload(2) and debug kernels

[Doug White]

On Sun, 16 Nov 2003 [EMAIL PROTECTED] 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
[EMAIL PROTECTED]  |  www.FreeBSD.org
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: kldload(2) and debug kernels

[Dimitry Andric]

On 2003-11-17 at 18:47:28 Doug White wrote:

 If you give a specific path to a module then it will load that module.

No. It will not load arbitrary files, but _only_ files that end in
.ko. I've encountered this before, and therefore I always simply
follow a make installkernel.debug by a script like:

  #!/bin/sh
  kernpath=/boot/kernel
  for i in ${kernpath}/*.debug; do mv $i `echo $i | sed s/\.debug$//`; done
  rm -fv ${kernpath}/linker.hints
  kldxref -v ${kernpath}

This is simply because I almost never keep a copy of /usr/obj after
installing, and it can be handy to debug later. I assume that all
debugging info is simply ignore by the boot and kernel module loaders,
but it can later be used by kgdb.


pgp0.pgp
Description: PGP signature