向非 Windows 操作系统添加蓝屏死机
我希望进入操作系统内核开发，并且一直在阅读有关操作系统的书籍（Tannenbaum ）以及研究 BSD 和 Linux 如何应对这一挑战，但仍然停留在几个概念上。
如果我想在操作系统上模仿 Windows 蓝屏死机，我是否可以简单地将这个逻辑放在 panic 内核方法？
是否有方法可以改进 Windows 目前执行此功能的方式？
I am looking to get into operating system kernel development and figured and have been reading books on operating systems (Tannenbaum) as well as studying how BSD and Linux have tackled this challenge but still am stuck on several concepts.
If I wanted to mimic the Windows Blue Screen of Death on an operating system, would I simply put this logic in the panic kernel method?
Are there ways to improve upon how Windows currently performs this functionality?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我不太确定在源代码中查找何处，但您可能想查看 ReactOS，这是一个已经出现 BSOD 的开源 Windows 克隆。
I'm not exactly sure where to look in the source but you might want to look into ReactOS, an open source Windows clone which has BSOD already.
BSD 实际上比使用 DDB 的 Windows 处理得更好:)
这是 FreeBSD 内核调试 文档的另一个链接。
BSDs actually handled this much better then Windows with DDB :)
Here's another link to FreeBSD Kernel Debugging docs.
您可以随时随地模拟 Windows 的错误检查功能。 大多数Linux系统将其放在XScreenSaver中。
但是，我怀疑这就是您真正要问的问题。 您是否询问如何生成转储文件？
为了改进 Windows 错误检查，Windows 驱动程序开发人员可以使用 KeRegisterBugCheckReasonCallback() 在生成的小型转储中记录有关其驱动程序状态的更多信息。 当未启用完整内核/内存转储时，这可能会提高事后调试的有效性。
You can emulate Windows's bugcheck functionality wherever you want. Most Linux systems put it in XScreenSaver.
However, I doubt that this is what you're really asking about. Are you asking how to generate a dump file?
To improve Windows bugchecks, Windows driver developers can use KeRegisterBugCheckReasonCallback() to record more information about the state of their drivers in the generated minidump. This potentially may improve the effectiveness of post-mortem debugging when full kernel/memory dumps are not enabled.