On Thu, 6 Mar 2025, Jeremy Drake via Mingw-w64-public wrote: > On Thu, 6 Mar 2025, Jacek Caban wrote: > > > Relying on __delayLoadHelper2 behavior specific to mingw-w64 comes with > > drawbacks. As I mentioned earlier, an application can forward the call > > to ResolveDelayLoadedAPI, which will bypass this change and fail to > > work, while it previously worked with earlier binutils. > > I tested this, and -ldloadhelper (which forwards to the OS API) does work > with current binutils.
Actaully, the test case I was starting with was delay loading from a non-existant module, and using the failure hook to load it. In the case of the ResolveDelayLoadedAPI function, it does not seem to save the function returned from the failure hook back to the delay IAT. Doing a more "normal" delay load of a function/module that *does* exist does result in a segfault with current binutils and ResolveDelayLoadedAPI. _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
