I am debugging code that is executing before the System startup breakpoint. When I look at Olly's Memory map window, I can identify some of the dlls, but they do not display any of their section names, don't have their "Names" (imports/exports) listed yet, etc. I'm guesssing they've been mapped to memory but not yet "loaded"? As I debug some of the code, I come across to a CALL that I identified as a GetProcAddress call. Whenever I attempt to step over the call, OllyDbg just sits there... displaying "Running" in the corner, but never breaking at the expected instruction. I can step in deeper and deeper, but I end up with the same problem down the line. If I set a breakpoint immediately after the call, and let Olly rip.. it will break on breakpoint and all is well. However, the GetProcAddress call is somehow loading a few other dlls into memory and executing code that I'm trying to find and debug. Why is OllyDbg dying when I try and step over certain calls? Has anyone else ever come across this?






