J
Jake Thompson
Hello,
I have an exe that calls a dll. The dll is dynamically loaded and I
use getprocaddress to get the address of the funciton I want to call.
Everything seems to work fine in debug mode but in release mode it is
blowing up at the first call to the dll. Does anybody have any advice
on how to narrow down the problem. I put popups into the exe code to
narrow down the issue to the first dll call but I am at a loss as to
what would cause debug dll to work and the release version not to work.
I can generate a map but I am terrible at reading it and I function a
lot better when the error occurs in debug mode because then I can use
the debug tool. Would the map be the best approach or is there a
better method. If I generate a map could someone help me find the
correct location in the dll?
Thanks
Jake
I have an exe that calls a dll. The dll is dynamically loaded and I
use getprocaddress to get the address of the funciton I want to call.
Everything seems to work fine in debug mode but in release mode it is
blowing up at the first call to the dll. Does anybody have any advice
on how to narrow down the problem. I put popups into the exe code to
narrow down the issue to the first dll call but I am at a loss as to
what would cause debug dll to work and the release version not to work.
I can generate a map but I am terrible at reading it and I function a
lot better when the error occurs in debug mode because then I can use
the debug tool. Would the map be the best approach or is there a
better method. If I generate a map could someone help me find the
correct location in the dll?
Thanks
Jake