调试故障转储:根据 VS2010,来自同一构建事件的二进制文件和符号文件不匹配
我收到了客户发来的故障转储文件,我正在尝试使用 VS2010 调试该转储文件。我已经检索了用于构建的源代码以及生成的符号文件,并且我向 VS 提供了包含它们的目录的路径;一切似乎都已就位。然而,当我尝试调试时,VS 报告该目录中包含的 .exe 或任何 .dll “没有匹配的二进制文件”。我使用 chkmatch 来比较一些二进制文件和符号文件,它报告它们匹配,时间戳和签名等等。我在网上搜索过,似乎没有人遇到过像我遇到的那么多麻烦,而且我找到的所有解决方案都是我已经做过的事情。
希望我忽略了一些简单的事情。
我缺少什么?如何确保 VS 将二进制文件与符号文件匹配?
I have received a crash dump file from a customer, and I am attempting to debug the dump file using VS2010. I have retrieved the source code we used for the build along with the generated symbol files, and I've provided VS with the path to the directory that contains them; everything seems to be in place. When I attempt to debug, however, VS reports that there is "no matching binary" for the .exe or any of the .dll's contained in that directory. I've used chkmatch to compare a few of the binaries and symbol files, and it reports that they match, time stamp and signature and all. I've searched around online and no one seems to have had as much trouble with this as I am encountering, and all the solutions I've found are things that I've already done.
Hopefully I'm overlooking something simple.
What am I missing? How can I ensure that VS matches the binaries to the symbol files?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
您可以使用WinDbg
启动 WinDbg 并加载转储文件(文件 > 打开崩溃转储)。
希望这有帮助。
You can use WinDbg
Download the tool (http://msdn.microsoft.com/en-us/windows/hardware/gg463016, you can use version 6.11.1.404 in order to avoid downloading the whole SDK) and install it.
start WinDbg and load the dump file (File > Open crash Dump).
Hope this helps.
另一件需要检查的事情是:如果同一产品的其他构建版本的二进制文件和符号位于符号路径中,我会遇到问题。
VS(我使用的是 2015)似乎没有搜索所有路径并选择正确的文件 - 我必须添加特定于我正在调试的故障转储的符号路径,并将这些路径在符号路径列表中“向上”移动首先找到并使用它们。
Another thing to check: I had problems if binaries and symbols for other build versions of the same product were in the symbol path.
VS (I'm using 2015) doesn't seem to search all the paths and choose the right files - I had to add symbol paths specific to the crash dump I'm debugging and move these "up" in the symbol path list for them to be found first and used.