WinDbg：如何让 WinDbg 的 Locals/Watch 支持复杂的 VB6 类型（集合、自定义类）？
首先，这可能吗？如果是这样我该怎么做？我对 Collection 类和自定义 VB 类特别感兴趣。
特别欢迎有关此主题的书籍/参考：我有“高级 Windows 调试”，但在分析涉及 VB6 组件的转储文件时我需要更多帮助。
一旦我必须开始检查 VB 对象的状态，我就不知所措了！
谢谢。
First, is this even possible? And if so how would I do this? I'm particularly interested in the Collection class and custom VB classes.
Particularly welcome would be a book/reference on this subject: I have "Advanced Windows Debugging", but I need more help when analyzing a dump file involving a VB6 component.
Once I have to start inspecting the state of VB objects, I'm in over my head!
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
据我所知，没有什么专门关于从 WinDBG 调试和可视化 VB6 对象的信息。
Matthew Curland 的书“针对日常程序员的高级 VB Power 技术”
可能是同类书籍中最好的一本书。
他确实研究了 VB6 类和堆栈的内存布局，这肯定会有所帮助（当我对堆栈中的返回地址进行逆向工程时，它对我帮助很大）。
也就是说，像 Collection 对象这样的东西内部相当复杂，所以它有多大帮助是有争议的。不过，从 WinDBG 解析更简单的“名称值对”类型对象应该相对简单。
As far as I know, there's nothing specifically out there about debugging and visualizing VB6 objects from WinDBG.
Matthew Curland's book, "Advanced VB Power techniques for everyday programmers"
Is probably the best book out there that kind of gets close.
He does work through the memory layouts of VB6 classes and the stack, which would definitely help (it helped me a TON when I was reverse engineering the return addresses off the stack).
That said, things like the Collection object are pretty complex internally, so how much it helps would be debatable. Simpler "name value pair" type objects should be relatively straightforward to resolve from WinDBG, though.