> I tested this scenario, and this problem only occurs with > dlopening cygwin1.dll. Not only cygwin1.dll, but also native dlls, e.g., kernel32.dll or user32.dll. I haven't tested the next release, but do you think it's the same reason for win32 dlls?