When an app being debugged triggers a "break on new module" breakpoint, is it possible to see where in the main app code it was called from ? I see the disassembly in the system API sitting on a RET instruction, and single-step F7 seems to issue a run command until the next module load. Examing the stack doesn't seem to help much either.

(Preferably here I would like to find the call to the LoadLibrary function that triggered the BP)

have you tried call stack (ALT+K) ?

Hmmm, LoadLibraryExA from OLE32. No mention of the application. I can only assume therefore that the app uses OLE to load it's libraries. Scary. On other app's I can see the actual place in the app where the library is loaded.

Cheers for the tip !