Question about loading of dlls during debug
-
I was trying to track down a bug (which one of the other developers was able to track down) and we noticed something strange in the debug output window (VC++ 6.0). After the app ends, the output window lists all the dlls that were loaded up, etc. I have the Trillian instant message interface installed and one of the dlls that is being loaded up is 'C:\Program Files\Trillian\events.dll'. Trillian has no relation to my app and is not being even remotely used, at least I think not. Does anyone know why this is happening? I am a junior developer, so there may be an obvious answer to this, but it seems very odd. Thanks!
-
I was trying to track down a bug (which one of the other developers was able to track down) and we noticed something strange in the debug output window (VC++ 6.0). After the app ends, the output window lists all the dlls that were loaded up, etc. I have the Trillian instant message interface installed and one of the dlls that is being loaded up is 'C:\Program Files\Trillian\events.dll'. Trillian has no relation to my app and is not being even remotely used, at least I think not. Does anyone know why this is happening? I am a junior developer, so there may be an obvious answer to this, but it seems very odd. Thanks!
the system is reporting events and the debug window is picking up on them. it's pretty much harmless. -c
-
I was trying to track down a bug (which one of the other developers was able to track down) and we noticed something strange in the debug output window (VC++ 6.0). After the app ends, the output window lists all the dlls that were loaded up, etc. I have the Trillian instant message interface installed and one of the dlls that is being loaded up is 'C:\Program Files\Trillian\events.dll'. Trillian has no relation to my app and is not being even remotely used, at least I think not. Does anyone know why this is happening? I am a junior developer, so there may be an obvious answer to this, but it seems very odd. Thanks!
The reason the dll is being loaded in your process is because it probably installs some sort of global hook via SetWindowsHookEx. The dll will then be loaded into all running processes. Chris Richardson Programmers find all sorts of ingenious ways to screw ourselves over. - Tim Smith
-
The reason the dll is being loaded in your process is because it probably installs some sort of global hook via SetWindowsHookEx. The dll will then be loaded into all running processes. Chris Richardson Programmers find all sorts of ingenious ways to screw ourselves over. - Tim Smith
Thanks Chris and Chris! Your responses were very helpful. :)