Shell32.dll constantly loaded/unloaded

[Nyte]

Sorry if this is the wrong forum section, but i don't know where else to put this.


When i deploy in debug mode, i see the following message continuesly in the debug log:

>=library-unloaded,id="C:\\Windows\\SysWOW64\\shell32.dll",t arget-name="C:\\Windows\\SysWOW64\\shell32.dll",host-name="C:\\Windows\\SysWOW64\\shell32.dll",thread-group="i1"
sLibrary C:\Windows\SysWOW64\shell32.dll unloaded

>=library-loaded,id="C:\\Windows\\SysWOW64\\shell32.dll",tar get-name="C:\\Windows\\SysWOW64\\shell32.dll",host-name="C:\\Windows\\SysWOW64\\shell32.dll",symbols-loaded="0",thread-group="i1"
sLibrary C:\Windows\SysWOW64\shell32.dll loaded

This doesn't really seem like normal behavior. Does anyone know what is happening?
Debugging is also terribly slow, most likely because of this.

[ChrisW67]

That is one of the core 32-bit Windows libraries being loaded/unloaded from a process memory space on your 64-bit system. I would expect it is never unloaded from RAM after first use. You are possibly getting this load message every time an exe or other library resolves a routine in the library for the first time, and the unload when the exe or other library is unloaded.

I have always found gdb on Windows to be very slow compared to its Linux equivalent. I do not really know why, but this level of tracing might have something to do with it.