DevPartner BoundsChecker 破坏了我的程序
我正在开发一个程序，我怀疑该程序存在一个或多个内存泄漏。 Stack Overflow 上的其他一些答案告诉我尝试 DevPartner BoundsChecker（我尝试过的许多其他答案之一）。
现在，当我在 BoundsChecker 运行的情况下运行我的程序时，它会崩溃。在某些时候，Windows 文件打开对话框将启动，并且在实际发生之前，会触发一个不可继续的断点。这仅在 BoundsChecker 运行时发生。
根据控制台输出，程序尝试执行的最后一件事是加载 C:\Windows\SysWOW64\slc.dll，DevPartner 将其识别为“Microsoft Software Licensing Client Dll”。由于我们在该特定程序中不使用任何软件许可，因此这必须以某种方式与应该打开的对话框窗口相关。
不管怎样，我真的很想找到那些内存泄漏，为此，我需要打开该文件。是否有可能告诉 BoundsChecker 不要因为这个问题而破坏我的程序（无论该问题是什么）？
I am working on a program which I suspect to have one or more memory leaks. Some other answer on Stack Overflow told me to try DevPartner BoundsChecker (one of many others I tried).
Now when I run my program with BoundsChecker running, it will break. At some point, a Windows file open dialog will get initiated and right before that actually happens, a non-continuable breakpoint gets triggered. This only happens with BoundsChecker running.
According to the Console Output, the last thing that the program is trying to do is to load C:\Windows\SysWOW64\slc.dll which DevPartner recognizes as the "Microsoft Software Licensing Client Dll". Since we do not use any software licensing in that particular program, this must somehow be related to the dialog window that is supposed to be opened.
Anyway, I really want to find those memory leaks and for that, I need to open that file. Is there a possibility to tell BoundsChecker not to break my program because of this issue (whatever that issue might be)?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
Basti，9.x 版本的 BoundsChecker 中存在 MFC 文件打开提示的已知错误。如果您发布 DPS 和 Visual Studio 版本，我也许可以告诉您需要哪个补丁或更新来解决此问题。另一方面，如果您确实遇到了许可保护 DLL，BoundsChecker 可能会激发其中的一些防篡改逻辑。我已经看到 DPS 在其他 Micro Focus 产品中提高了防篡改逻辑。如果是后者，您需要向 Micro Focus 客户服务部门提出案例并提供重现测试样本。无耻插件：我在 DevPartner 团队工作。我们将于 2011 年 2 月 4 日发布带有 BoundsChecker 的 DPS 10.5，以支持 x64 应用程序。下载评估发布后，请查看此版本是否可以解决您的问题。
Basti, there was known bug in the 9.x versions of BoundsChecker with the MFC file open prompt. If you post your DPS and Visual Studio versions I might be able to tell you which patch or update you need to get around this. On the other hand if you really are tripping up in a licensing guard DLL, BoundsChecker may be exciting some anti-tamper logic in it. I have seen DPS raise the anti-tamper logic in other Micro Focus products. If it is the latter you would need to raise a case with Micro Focus customer care and provide a repro test sample. Shameless plug: I work on the DevPartner team. We are releasing DPS 10.5 with BoundsChecker for x64 application support on February 4, 2011. Please see if this version corrects your issue once the download eval is posted.