How to symbolicate crash report using .pdb file

不羁的心 提交于 2019-12-11 04:31:11

问题


I've a crash report. It's not symbolicated. I've .pdb file, source code and the package, is there any way to turn this stack trace to meaningful method names using .pdb file?

Exception Stack:
SharedLibrary!<BaseAddress>+0x3f7d77
MyApp!<BaseAddress>+0x52b4d7
MyApp!<BaseAddress>+0x59ed69
MyApp.API.GetFilter()
MyApp!<BaseAddress>+0x66f79f
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
SharedLibrary!<BaseAddress>+0x368a33
SharedLibrary!<BaseAddress>+0x369031
SharedLibrary!<BaseAddress>+0x369b49
SharedLibrary!<BaseAddress>+0x369b0f
MyApp!<BaseAddress>+0x67293f
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
SharedLibrary!<BaseAddress>+0x368a33
SharedLibrary!<BaseAddress>+0x369031
SharedLibrary!<BaseAddress>+0x369b49
MyApp!<BaseAddress>+0x69d129

回答1:


If you uploaded a .pdb along with your build. They likely do not match, ensure that your checksum and binary image UUID's match.

In order to verify if you have the correct symbols:

  1. Check the id of the symbol files uploaded on the Files tab under Version
  2. Check if this matches the Binary image's under crash's log
  3. If these match you'll be able to see symbolicated crash reports


来源:https://stackoverflow.com/questions/44045385/how-to-symbolicate-crash-report-using-pdb-file

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!