Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test LM_EnumSymbols for external processes #203

Closed
rdbo opened this issue Mar 6, 2024 · 1 comment
Closed

Test LM_EnumSymbols for external processes #203

rdbo opened this issue Mar 6, 2024 · 1 comment

Comments

@rdbo
Copy link
Owner

rdbo commented Mar 6, 2024

There is a chance it might fail on windows due to the way it is currently implemented (loading the module in the current process) for EXE files.

@rdbo
Copy link
Owner Author

rdbo commented May 31, 2024

It works but might cause issues later due to using the deprecated DONT_RESOLVE_DLL_REFERENCES
From:

DONT_RESOLVE_DLL_REFERENCES 0x00000001

If this value is used, and the executable module is a DLL, the system does not call [DllMain](https://learn.microsoft.com/en-us/windows/desktop/Dlls/dllmain) for process and thread initialization and termination. Also, the system does not load additional executable modules that are referenced by the specified module.

Note  Do not use this value; it is provided only for backward compatibility. If you are planning to access only data or resources in the DLL, use LOAD_LIBRARY_AS_DATAFILE_EXCLUSIVE or LOAD_LIBRARY_AS_IMAGE_RESOURCE or both. Otherwise, load the library as a DLL or executable module using the [LoadLibrary](https://learn.microsoft.com/en-us/windows/desktop/api/libloaderapi/nf-libloaderapi-loadlibrarya) function.

It tells us to not use this value and use those other ones instead, but the other ones don't work...

@rdbo rdbo closed this as completed May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant