The caller should assume that the driver can be unloaded at any time unless the caller can guarantee otherwise. This pointer remains valid only while the driver remains loaded. Each ImageBase value is a pointer to the base of a loaded driver image. If a call to AuxKlibQueryModuleInformation succeeds, the routine writes an ImageBase value to each element in the QueryInfo array. As a result, the second call to AuxKlibQueryModuleInformation might return STATUS_BUFFER_TOO_SMALL even if the driver allocates a buffer that is based on the size that was obtained from the first call. The number of loaded modules can change between the first and second calls to AuxKlibQueryModuleInformation. After AuxKlibQueryModuleInformation returns, the buffer contains an array of module information. This time, the QueryInfo pointer must contain the address of the allocated buffer. After AuxKlibQueryModuleInformation returns, the location that the BufferSize parameter points to will contain the number of bytes that the driver will have to allocate for the array.Ĭall a memory allocation routine, such as ExAllocatePoolWithTag, to allocate a buffer for the array.Ĭall AuxKlibQueryModuleInformation again.
To obtain information about the operating system's loaded image modules, a driver must:Ĭall AuxKlibQueryModuleInformation with a NULL QueryInfo pointer. The routine might return other NTSTATUS values. AuxKlibQueryModuleInformation returns STATUS_BUFFER_TOO_SMALL if the QueryInfo pointer is not NULL and the driver-supplied BufferSize value is too small. Return valueĪuxKlibQueryModuleInformation returns STATUS_SUCCESS if the operation succeeds. If this pointer is NULL, AuxKlibQueryModuleInformation writes the required buffer size to the location that BufferSize points to. This value must be sizeof( AUX_MODULE_BASIC_INFO) or sizeof( AUX_MODULE_EXTENDED_INFO).Ī pointer to an array of AUX_MODULE_BASIC_INFO or AUX_MODULE_EXTENDED_INFO structures that receives information about loaded image modules. The size, in bytes, of each element of the array that QueryInfo points to.
If QueryInfo is not NULL, the location must contain the specified number of bytes. If QueryInfo is NULL, the location receives the number of bytes that the driver must allocate for the array that receives the retrieved information. Syntax NTSTATUS AuxKlibQueryModuleInformation(Ī pointer to a location that contains or receives a buffer size, in bytes. I have also looked at a very near answer to my questionĪdding a `.The AuxKlibQueryModuleInformation routine retrieves information about the image modules that the operating system has loaded. Somebody just saying."Here's my gradle file" really hurts more than than it helps some times because it does not make you smarter just copying it. The issue I am having with gradle at the time is I really don't understand what is relevant to the thing I am doing vs what you find on the internet. Is one supposed to some how associate the Klib with a package? Is there a default folder structure to put the. Is one supposed to use gradle and add a dependency of the klib file? klib file, call it "XXX.klib", how do we import the symbols? The flow to utilize a C library in Kotlin is easy to find.Ģ) use the tool cinterop on the. And YES, I tried to read about everything before I asked the question. There is documentation out there and a couple tutotials that get you 85% and just miss the mark. I am new to Kotlin/Native as I assume many others are and wish to use a C library from Kotlin.
0 kommentar(er)
