Expand on Chris' investigation of debugging a blank screen RNW app in Release via WinDbg.
Can we get a list of modules by name that have thrown exceptions? Can we get information on what those exceptions are, or where in the module's code they have taken place?
We should figure out how to get this information via WinDbg and add to the existing document we have on debugging RNW apps with WinDbg. This way developers can follow the steps to get more information.
Long term we could create a WinDbg extension that runs the steps automatically and spits out data.
Expand on Chris' investigation of debugging a blank screen RNW app in Release via WinDbg.
Can we get a list of modules by name that have thrown exceptions? Can we get information on what those exceptions are, or where in the module's code they have taken place?
We should figure out how to get this information via WinDbg and add to the existing document we have on debugging RNW apps with WinDbg. This way developers can follow the steps to get more information.
Long term we could create a WinDbg extension that runs the steps automatically and spits out data.