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

Why is the delay loading mechanism not used for delay loaded imports? #76

Open
Dewera opened this issue Dec 3, 2020 · 0 comments
Open
Assignees
Labels
bug Something isn't working
Milestone

Comments

@Dewera
Copy link

Dewera commented Dec 3, 2020

When a delay load import is used by a PE the linker generates the typical stub that calls LoadLibrary/GetProcAddress and writes this value into the IAT when referenced for the first time. Is there a reason why this behavior wasn't left intact and delay loaded imports are forcibly loaded during the mapping process via LoadLibrary, defeating the actual purpose of delay loading imports in the first place?

From my testing earlier in the year as long as you correctly map the sections and apply relocations the linker generated stub works as intended.

@TheWover TheWover self-assigned this Apr 15, 2021
@TheWover TheWover added the bug Something isn't working label Apr 19, 2021
@TheWover TheWover added this to the v0.9.3 milestone Apr 19, 2021
@TheWover TheWover modified the milestones: v0.9.3, v1.1 Feb 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants