I have started debugging c# program using WinDbg.
Initially used GFlags to put break point on a very begin as it crashes asap it's being run.
From WinDbg after fetching gflag's break point, doing continue ("g") it proceeds execution and crashes at the end with the trace:
I have crossed custom .dll-s as they're confidential.
If I am not wrong "e0434352" stands for a very generic CLR exception.
Is there any way how to could I inject SOS into WinDbg to make this trace more precise? e.g. How to translate these generic e0434352 exceptions into C# ones to find the exact cause of the problem?