Unloading DLLs in Visual Studio - PDB Locked

[Douglas Cox]

So we have a version of runtime-recompiling in our engine, and we were trying to unload our DLL, copy the new DLL over it, and load the new one.

This works except when the debugger is attached because even though it gets the DLL unload notification, VS2012 seems to keep the DLL's PDB file locked for some reason.  I was just wondering if you guys had run into anything like this?  There was a VS2012 patch recently that fixed a PDB locking issue even after the debugger quit, but we're using that and still have this problem.

We're about to try the "/Z7" option to not generate PDBs, but I'm not sure what other issues that will cause.  And we'd obviously like to avoid VS wasting more and more memory each reload.

Thanks for any theories!

-Doug

[Doug Binks]

We've not come across this issue as we currently don't unload DLLs. This might become an issue on 32-bit systems where virtual memory is limited, but so far I've not encountered any problems.

--
You received this message because you are subscribed to the Google Groups "Runtime-Compiled C++" group.
To unsubscribe from this group and stop receiving emails from it, send an email to runtimecompiledcpl...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.