Internet Explorer 8 在哪里存储其故障转储?

发布于 2024-08-05 01:57:20 字数 173 浏览 4 评论 0原文

我正在对抗一个错误,该错误不会在我的机器上重现,但每次都会在我客户的机器上重复。我已经尝试了一切,现在我正在寻找 IE8 崩溃后留下的任何调试数据(或其他数据)。谷歌和微软的搜索没有给我任何结果。 Internet Explorer 8 在哪里存储其故障转储?它肯定会在崩溃后向 Microsoft 发送一些内容,我如何才能看到它?

I am fighting a bug which does not reproduce on my machine, but repeats every time on my client's machine. I've tried everything, and now I am looking for any debug data (or whatever) that IE8 leaves after a crash. Google and Microsoft searches gave me nothing. Where does Internet Explorer 8 store its crash dumps? It definetely sends something to Microsoft after a crash, how can I see it?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

人疚 2024-08-12 01:57:20

这里有一篇文章将向您展示如何生成小型转储

http://www.vistax64.com/windows-updates/227276-mshtml-dll-internet-explorer-8-crash-3.html

要生成小型转储:

  1. 下载 安装“调试工具”包
  2. 并从安装的文件夹中 以管理员身份运行 WinDBG.exe(右键单击“以管理员身份运行...”)。
  3. 按F6,“按可执行文件”排序,找到IEXPLORE.EXE,选择,确定。 (如果此时您只运行一个 IEXPLORE 实例,那就更容易了。)
  4. 它会喷出一大堆数字,并最终将您转至页面底部的提示符上。只需输入 G 并按 Enter 键即可。这会将调试器附加到 IEXPLORE 进程,但随后让它“Go”并继续执行其操作。
  5. 做任何你需要做的事情来重现崩溃。
  6. 这次,崩溃情况将导致调试器“闯入”IEXPLORE 进程并暂停其所有操作。换句话说,您不会看到相同的崩溃消息,而是会看到调试器接管并且 IEXPLORE 看起来像是被冻结了。
  7. 再次忽略所有喷涌,等待 WinDBG 窗口底部的提示,然后输入以下内容:

    .dump /m IE1.dmp

如果您没有提供完整路径,则将在安装调试器包的同一文件夹中创建 IE1.dmp 文件。如果您压缩该小型转储并将其上传到此处,我或其他人可能能够从中挖掘更多信息。

There is a post here that will show you how to generate a mini dump

http://www.vistax64.com/windows-updates/227276-mshtml-dll-internet-explorer-8-crash-3.html

To generate a minidump:

  1. Download and install the "Debugging Tools" package
  2. From the folder where you installed it, run WinDBG.exe as admin (right-click, "run as admin...").
  3. Press F6, sort "by executable", find IEXPLORE.EXE, select, OK. (It's easier if you have only one instance of IEXPLORE running at this time.)
  4. It'll spew out a whole bunch of numbers and eventually dump you on a prompt at the bottom of the page. Just type G and press enter. This attaches the debugger to the IEXPLORE process but then lets it "Go" and continue to do its thang.
  5. Do whatever you need to do to repro the crash.
  6. This time, a crash condition will cause the debugger to "break into" the IEXPLORE process and suspend all its actions. In other words, instead of seeing the same crash message you'll see the debugger take over and IEXPLORE will look like it's frozen.
  7. Ignore all the spew again and wait for the prompt at the bottom of the WinDBG window, then type this:

    .dump /m IE1.dmp

If you don't give it a full path, the IE1.dmp file will be created in the same folder where you installed the debugger package. If you zip up that minidump and upload it here, I or someone else may be able to dig more info out of it.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文