no KLD symbols in dtrace?

[Chuck Tuffli]

On Fri, Apr 22, 2011 at 9:41 AM, Andriy Gapon <avg at freebsd.org> wrote:
> on 22/04/2011 18:56 Chuck Tuffli said the following:
>> On Fri, Apr 22, 2011 at 8:44 AM, Andriy Gapon <avg at freebsd.org> wrote:
>>> Also, dtrace process needs to access the module file for address-to-name translation.
>>
>> Hmm ... I'm building this module out of tree. Where does dtrace look
>> for modules?
>
> I think that exactly at the place from which a module is loaded.
> You can double-check with kldstat -v, e.g.:
>  2    1 0xffffffff80c6c000 217f20   zfs.ko (/boot/kernel/zfs.ko)

Ah-ha! I was loading the module with a relative path (i.e. kldload
./ocs.ko), but when I switched this to use the full path (i.e. kldload
/home/ctuffli/ocs.ko) everything worked.

  2  33759       bus_release_resource:entry
              ocs.ko`ocs_release_bus+0x2e
              ocs.ko`ocs_pci_detach+0x31
              kernel`device_detach+0x84
              kernel`driver_module_handler+0x37c
              kernel`module_unload+0x49
              kernel`linker_file_unload+0x178
              kernel`kern_kldunload+0x117
              kernel`syscallenter+0x23d
              kernel`syscall+0x4b
              kernel`0xffffffff808c5572

Thanks for the patch and all your help!

---chuck