Alternative LoadLibrary for BuildImportTable about memorymodule HOT 6 CLOSED

Line 249 is what you're looking for, just check there for the string of the function name you want to override and give it the address of the function it should call.

from memorymodule.

@icefex thanks for the response, however I was thinking on a more modular way than overwrite the code of MemoryModule

MemoryModule is provided under MPL license, so I want to avoid modifications to it to the minimum and instead have a hooks friendly API to be able, from another module, hook library loading.

from memorymodule.

You have to extend MemoryModule in some way, the license is not the issue here. Like you said just keep it minimal and share the changes :D

You could f.i. implement the whole shebang as a function call to another module, just share the patch with that line in it and you're good to go. (Tip: if you are going to hook more than a few calls implement a global linked list in which you register the hooked calls, this allows for changes in the hooks at runtime and will look better).

from memorymodule.

Having an API to override the LoadLibrary/GetProcAddress called by MemoryModule probably would be the cleanest solution. I'm open for patches or pull requests ;-)

from memorymodule.

You'll experience some problems with TLS/FLS data, if you load a complete executable with MemoryLoadLibrary. TLS has it's own directory. You've to implement to following steps:

• Loading all dependencies and resolve the import tables
• Initialize TLS of all dependencies( Call TLS Callbacks, allocate indices )
• Iterate through the dependencies and call every DLLMain
• Initialize TLS of the executable/library to execute
• Call the entry point

from memorymodule.

Please check the latest code, is this what you were looking for?

from memorymodule.