在一个侧面加载的Windows应用商店应用的日志中,我发现了以下异常:
Arg_ArgumentException --> System.ArgumentException: Arg_ArgumentException at SharedLibrary!<BaseAddress>+0x3a13ad at my-app!<BaseAddress>+0xf29d82h at my-app!<BaseAddress>+0xf29cdc at my-app!<BaseAddress>+0x10e0844 at my-app!<BaseAddress>+0x14fbe60 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at SharedLibrary!<BaseAddress>+0x502089 at System.Threading.ContextCallback.Invoke(Object state) at SharedLibrary!<BaseAddress>+0x3e683c
为了将跟踪符号化,我尝试使用corefx-tools的WindowsDevCenterStacktraceSymbolicater和StackParser以及应用程序的PDB,它会将跟踪更改为:
Arg_ArgumentException --> System.ArgumentException: Arg_ArgumentException at SharedLibrary!COM+_Entry_Point+0x3a13ad at my-app!COM+_Entry_Point+0xf29d82 at my-app!COM+_Entry_Point+0xf29cdc at my-app!COM+_Entry_Point+0x10e0844 at my-app!COM+_Entry_Point+0x14fbe60 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at SharedLibrary!COM+_Entry_Point+0x502089 at System.Threading.ContextCallback.Invoke(Object state) at SharedLibrary!COM+_Entry_Point+0x3e683c
在这种情况下,有没有办法解决COM+_Entry_Point引用问题?多么?
发布于 2019-10-11 21:48:01
不要将PDB放在应用程序的输出文件夹中,而要使用放在ilc子目录中的PDB文件(这个目录要大得多)。有了这个PDB,堆栈跟踪将使用上面提到的工具之一正确地进行符号化。
https://stackoverflow.com/questions/58342029
复制相似问题