samedi 7 mars 2015

Analyze crash in unavailable DLL on Windows Phone such as TextInputFramework.dll and CoreUIComponents.dll


I have a XAML WebView. It happens that whenever I swipe on the software keyboard to provide text input to it, my app crashes with the following call stack:



TextInputFramework.dll!73719cc0() Unknown
TextInputFramework.dll!73715b3a() Unknown
TextInputFramework.dll!7371fcd2() Unknown
TextInputFramework.dll!7371f682() Unknown
TextInputFramework.dll!7371fc54() Unknown
TextInputFramework.dll!73715a02() Unknown
TextInputFramework.dll!73710e7e() Unknown
TextInputFramework.dll!737135a2() Unknown
CoreUIComponents.dll!759e4448() Unknown
CoreUIComponents.dll!759a32ee() Unknown
CoreUIComponents.dll!75a089cc() Unknown
CoreUIComponents.dll!75a08104() Unknown
CoreUIComponents.dll!75a06ed2() Unknown
CoreUIComponents.dll!75a06b08() Unknown
CoreUIComponents.dll!75a05604() Unknown
CoreUIComponents.dll!759a7e64() Unknown
[External Code]


Is there any method to analyze the reason for this kind of crashes where I have not the available *.pdb? I have no idea why the trace ends with [External Code] providing no information whatsoever about the crash. My guess is that it is due to some crash originates from the software keyboard which executes independently from my app [like a system service] so there is no link to my code.




Aucun commentaire:

Enregistrer un commentaire