在windbg中,什么会导致消息“警告:无法验证mydll.dll的时间戳”?
我有一个转储(由 SysInternal 的 procdump
创建),当我要求查看线程的调用堆栈时,我收到错误:
"WARNING: Unable to verify timestamp for mydll.dll"
我拥有 mydll.dll
的源代码我有它的 PDB 文件,调用堆栈似乎有效,但我想知道导致该消息的原因是什么。过去我没有收到该警告消息。
谢谢。
I have a dump (created by SysInternal's procdump
) and when I ask to view the call stack of a thread I get the error:
"WARNING: Unable to verify timestamp for mydll.dll"
I own the source code for mydll.dll
and I have the PDB
file for it, the call stack seems valid but I would like to know what can be the cause of the message. In the past I did not get that warning message.
Thank you.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(4)
检查您是否正在使用小型转储。如果是,那么您必须提供附加信息,即二进制路径(exe\dll 路径)以添加 exepath 执行此命令 -
.exepath+“dll\exe 的路径”
Check if you are using mini dump. If yes then you have to provide additional info which is binary path (exe\dll path) to add exepath execute this command -
.exepath+ "Path of dll\exe"
原因可能是您没有 mydll.dll 的二进制文件
可用。
尝试将其放在与 .pdb 相同的位置或使用文件 ->图片路径
指向该位置。请注意,.pdb 和 .dll 必须与转储的程序版本相同。
The reason might be that you don’t have the the binary for your mydll.dll
available.
Try to either put it in the same location as the .pdb or use the File -> Image path to
point at the location. NB both the .pdb and .dll must be the same version as the program dumped.
我得问一下。您正在使用的 dll 上的文件时间戳是否与创建转储的 dll 的时间戳匹配?
这可能是导致问题的一个简单原因。如果您重建了 DLL,或者获取了错误的版本,那么修复似乎很简单。
I have to ask. Does the file timestamp on the dll you are using match the timestamp of the dll that created the dump?
That would be one easy reason for the problem. If you have rebuilt the DLL, or grabbed the wrong version it seems like an easy fix.
这是因为您有一个小型转储,并且转储中不存在 mydll.dll 的时间戳。如果将原始 mydll.dll 添加到二进制路径 (
.exepath
),您将消除该警告。This is because you have a minidump and the timestamp for mydll.dll is not present in the dump. If you add the original mydll.dll to the binary path (
.exepath
) you will get rid of the warning.