Debugger not detaching from symbol database when dll closes

[Andrew_Smith]

I have an unusual situation here, but one which gives me a rapid development cycle (or did before).

I have an Fortran dll attached to a Smalltalk EXE. Since the exe is able to open and close its dll on command, I do not have to stop the exe to re-compile the dll and once the dll is re-compiled the exe can the start the dll as needed. This makes for a rapid development cycle. But with IVF 11.1.65 it no longer closes the debug database when the dll closes. I can get round this by detaching the debugger (VS2008) but this lengthens the development cycle beacuse I now have a detach and re-attach for each cycle. Since I may have several similar exe's running I have to be careful which one I attach to.

Can the debug database not closing properly be fixed?

[IanH]

I'm also experiencing this in similar situations (DLL loaded on-demand by Matlab/DLL loaded on-demand by Excel), but had mistakenly (given you are seeing it wth VS2008) put it down to being a VS2005 problem associated with a recent patch rather than IVF.

I've found that if you (accidentally) use "Stop debugging", rather than detaching, the pdb also remains open (even if the EXE that was hosting the DLL is closed), and a restart of VS2005 is required before you can complete a build again. Process explorer confirms that a (perhaps two?) file handle to the pdb is being held by VS, despite there being no active debugging. Having to restart VS is a right royal pain so I've continued to bind Shift-F5 to detach in the meantime.

This on xp professional with sp3, vs2005 with sp1 + vista update and ivf 11.1.065.

[Steven_L_Intel1]

As far as I know, no IVF component opens the PDB - this is all done by Visual Studio.