Re: kld(): Undefined Symbols error
Re: kld(): Undefined Symbols error
- Subject: Re: kld(): Undefined Symbols error
- From: "Brian Bechtel" <email@hidden>
- Date: Tue, 1 Aug 2006 09:56:48 -0700
On 8/1/06, Dinesh Bhat <email@hidden> wrote:
Hi there,
Whenever I add IOWorkLoop and try loading the kext, I get the following
error.
kld(): Undefined symbols:
__ZN26com_linsys_driver_receiver11getWorkLoopEv
__ZN26com_linsys_driver_receiver15handleInterruptEv
__ZN26com_linsys_driver_receiver16enableInterruptsEv
__ZN26com_linsys_driver_receiver16interruptOccuredEP8OSObjectP22IOInterruptEventSourcei
You have unresolved symbols. To determine the real name of the
symbols, use "c++filt" on the symbol name, with the extra underscore _
removed from the beginning of the symbol name. For example:
c++filt _ZN26com_linsys_driver_receiver11getWorkLoopEv
c++filt _ZN26com_linsys_driver_receiver15handleInterruptEv
c++filt _ZN26com_linsys_driver_receiver16enableInterruptsEv
c++filt _ZN26com_linsys_driver_receiver16interruptOccuredEP8OSObjectP22IOInterruptEventSourcei
Gives you symbol names of
com_linsys_driver_receiver::getWorkLoop()
com_linsys_driver_receiver::handleInterrupt()
com_linsys_driver_receiver::enableInterrupts()
com_linsys_driver_receiver::interruptOccured(OSObject*,
IOInterruptEventSource*, int)
Now you need to determine how to resolve those symbols. For that, I
can't help. You have not given enough information.
Good luck.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden