我正在开发一个多平台 C++ 模糊测试应用程序。该应用程序生成一个子进程并检查它是否意外停止。我已经设法在 Linux 上做到这一点，但是，Windows 异常处理机制让我的事情变得很困难。
我的代码现在执行以下操作：
- 调用 CreateProcess 来生成进程。
- WaitForSingleObject 等待它终止。
- 然后调用 GetExitCodeProcess 并检查退出代码是否对应于异常。
一切都按预期工作，我已经使用空解除引用测试应用程序对其进行了测试，并且我可以优雅地捕获异常。然而，每次我对此进行测试时，都会出现一个 Windows 错误消息框，告诉我发送或不发送错误报告。由于模糊器应该是一个自动测试应用程序，因此我需要以某种方式禁用此通知，这样即使捕获到异常，模糊器也可以继续测试。
我已经尝试安装 SEH 处理程序，但没有运气（显然这些处理程序不是由子进程继承的）。我读过一些有关使用向量异常处理的内容，但假设它是相同的，我相信向量处理程序不是继承的。
有人可以帮我解决这个问题吗？我不知道要搜索什么，我已经用谷歌搜索了很多，但没有找到任何东西。
谢谢！
i'm developing a multi-platform C++ fuzzing application. The app spawns a child process and checks whether it stopped unexpectedly. I've already managed to do this on linux, however, windows exception handling mechanism is making things hard for me.
My code right now does the following:
- Call CreateProcess to spawn the process.
- WaitForSingleObject to wait for it to terminate.
- Then call GetExitCodeProcess and check if the exit code corresponds to an exception.
Everything works as it should, i've tested it with a null dereferencing test application, and i can catch the exception gracefully. However, each time i test this, a Windows error message box spawns telling me to Send or Not Send the error report. Since the fuzzer is supposed to be an automatic testing application, i'd need to somehow disable this notification, so that even if an exception is caught, the fuzzer can continue testing.
I've already tried installing a SEH handler, but had no luck(apparently these handlers aren't inherited by child processes). I've read something about using vectored exception handling, but suppose it would be the same, i believe vector handlers aren't inherited.
Could anybody help me with this problem? I don't know what to search for, i've already googled a lot and haven't found anyhing.
Thanks!
发布评论
评论（3）
调试 API 是一种选择。 此处是 MSDN 中的起点。
Debug API is one option. Here is a starting point in MSDN.
根据frast的答案，您可以将进程作为具有合适子生成=VS.85%29.aspx" rel="nofollow">设置错误模式。此（可继承）设置确定哪些错误将导致弹出对话框 - 我在尝试为自动化测试应用程序实现完全相同的事情时发现了您的问题。
为了避免任何错误对话框，使用
注入可能有点过分 - 最好使用包装器进程。
Following on frast's answer, you can spawn the process as a child of a process with a suitable SetErrorMode. This (inheritable) setting determines which errors will result in dialogs popping out - I found your question while trying to achieve the exact same thing for an automated testing application.
To avoid any error dialogs, use
Injection is probably overkill - better to use a wrapper process.
尝试将以下代码注入您的子进程：
查找
在这里阅读有关注射技术的信息：
导入表内的注入代码
Try to inject the following code into your child process:
Lookup the details of SetErrorMode in MSDN.
Read about injection technique here:
Injective Code inside Import Table