Unresolved symbols in kernel dll..

Hi,

I am seeing the issue where while building the export driver, .lib is generated but it throws unresolved external symbols while building .sys file.

At the same time, if I build using DRVIER_LIBRARY, it builds fine. I am wondering what is being missed in export driver build?

Any response appreciated.

Thanks.

Can you post the name of this unresolved symbol ? Does your export driver exports DllInitialize and DllUnload ? Do you have a DriverEntry ?

Hi,

Yes I do have DllInitialize and DllUnload in the def file. I have DriverEntry in my export driver also.

These unresolved symbols are some private functions which are being used in the driver BUT the same code builds if I change the TARGET_TYPE (EXPORT_DRIVER to DRIVER_LIBRARY). I wonder why.

Thanks.

What are the specific names the linker is complaining about? Post the output. Do the names start with “_”, have “@” at the end? A bunch of random characters (Are you using C++?) at the end ?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Friday, October 31, 2014 8:08 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Unresolved symbols in kernel dll…

Hi,

Yes I do have DllInitialize and DllUnload in the def file. I have DriverEntry in my export driver also.

These unresolved symbols are some private functions which are being used in the driver BUT the same code builds if I change the TARGET_TYPE (EXPORT_DRIVER to DRIVER_LIBRARY). I wonder why.

Thanks.


NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Since DRIVER_LIBRARY is just a LIB which is not a loadable file, it doesn’t care about unresolved symbols. But when you build an actual loadable binary (EXPORT_DRIVER), all symbols have to be resolved either within the binary, or imported.

Thanks guys for the responses, that helps.

I do see only “error LNK2001: unresolved external symbol function_name” in my build.
These functions are picked up internally developed headers which are panicking.

Thanks.

Dear god, just follow directions. Copy and paste the specific errors from the log and send it to the list. It could be you are missing extern “C”. could be mismatched calling convenctions. It could by any other number of things

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Friday, October 31, 2014 1:08 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Unresolved symbols in kernel dll…

Thanks guys for the responses, that helps.

I do see only “error LNK2001: unresolved external symbol function_name” in my build.
These functions are picked up internally developed headers which are panicking.

Thanks.


NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer