Hi All, I'm trying to debug a dll directly with Olly but not having any luck. When I load it and step over the code, it immediately goes into one of it's imports (msvbvm60.dll) which calls the function GetCurrentThreadId, then goes to kernel32 where ExitThread is called and the process terminates. This all happens within 30 or so steps and apart from the first 3 lines, it never even reaches the main Dll. I know kernel32.dll has IsDebuggerPresent but that function isn't called so I'm wondering why it would exit so quickly?
Thanks...

I had this happen once before, I believe you must also process the file that calls the dll, because since there is no direct access, its first instinct is to quit.

Thanks for the reply. ..

I was hoping to avoid that because the host exe has IsDebuggerPresent and also Olly comes up saying adlm.dll has possible self modifying code. When I step over it, something about Interlock comes up. All these things add to my confusion so I was trying to isolate the cuplrit. I guess it only makes sense that it won't run properly without the host... Back to the drawing board!!!!