Mixed assembly crashes on exit

[=?Utf-8?B?SmltIFdhbHNo?=]

VS2005 - VC++/MFC: most modules compiled as native. Two modules compiled as
/clr (managed). One of these two modules uses a .NET C# Windows form User
control in an MFC dialog box.

The program seems to run fine, but crashes when I exit.

The same crash occurs even if I immediately exit when the program window
opens.

I have reproduced the problem on two development systems. While the final
error is different on the two systems, is different, it occurs in the same
general area. I have tracked the code to MINTERNAL.H,
ModuleUninitializer::SingletonDomainUnload(). It is using a C++ for each
statement to iterate through a collection of handlers presumably to unload
the modules of the program. It is possible that this collection has gotten
corrupted.

Help! I think I am in over my head with this problem.

Thanks,
Jim

[Scot T Brennecke]

Jim,
Do you have DebugDiag installed? If not, download it:
Download details: Debug Diagnostic Tool v1.1:
http://www.microsoft.com/downloads/d...DisplayLang=en

Do you have a symbol server cache set up on your machine? If not, do this:
Use the Microsoft Symbol Server to obtain debug symbol files:
http://support.microsoft.com/kb/311503
Using a Symbol Server (Visual Studio Debugging):
http://msdn.microsoft.com/library/en...asp?frame=true

Once you have these things set up (if not already), use DebugDiag to monitor your application
and generate a crash dump when it occurs.

If you don't get enough clues to solve this on your own, post back here for more guidance.

"Jim Walsh" <Ji******@discussions.microsoft.comwrote in message
news:F1**********************************@microsof t.com...

VS2005 - VC++/MFC: most modules compiled as native. Two modules compiled as
/clr (managed). One of these two modules uses a .NET C# Windows form User
control in an MFC dialog box.

The program seems to run fine, but crashes when I exit.

The same crash occurs even if I immediately exit when the program window
opens.

I have reproduced the problem on two development systems. While the final
error is different on the two systems, is different, it occurs in the same
general area. I have tracked the code to MINTERNAL.H,
ModuleUninitializer::SingletonDomainUnload(). It is using a C++ for each
statement to iterate through a collection of handlers presumably to unload
the modules of the program. It is possible that this collection has gotten
corrupted.

Help! I think I am in over my head with this problem.

Thanks,
Jim