debugging - Reducing the size of minidumps of managed programs while keeping some heap information? -


With dump debugging support in .NET 4.0 we are automatically seeing (after asking the user of course). The C # program crashes to upload them to our issue tracking system (so that MIDDLEPS can help resolve the cause of the crash).

Everything is working fine when using the WithFullMemory minidump type, we can see both the Stack and Hap Variables. Unfortunately, (zip) dumps are too large for small C # programs too.

If we use the "normal" minidump type, then we get a very small dump, but managed debugger. In fact, nothing less than FofelMiri is quite useless in the managed debugger. We have made some attempts to use our module MINIDUMP_CALLBACK_ROUTINE to limit the module information included, but it seems that there is almost no effect on the managed dump, but is it still successful to break managed debugging?

Is there any suggestion on how to trim the minidump when keeping this useful for managed debugging?

I use the following flags to create space for the C ++ applications to generate useful minidump :

  MiniDumpWithPrivateReadWriteMemory | MiniDumpWidgetSegas | MiniDampHandHandleData | MiniDampWithFullMarineFFO | MiniDumpWiththifefoin MiniDumpWithUnloadedModules  

The flag values ​​are specified in DBGRPH and will need to be martial in C #. Dump is restricted by specifying the callback routine.


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -