向后调试 [英] Debugging backwards
问题描述
我有两个问题：
-
在进行源代码级调试（使用任何调试器）时，任何调试器都可以保存一些迭代/ for-loop /执行的任何代码，并允许用户在调试期间的稍后时间点返回到先前执行的代码/数据状态。
需要这是一些变量/指针在执行期间的某个时间早被破坏，但是在执行代码后的某个时间/之后被访问，当它崩溃/挂起代码时，所以我想去返回看看哪个函数/什么时候变量被破坏/错误的值计算并写入它？有可能在任何调试器（gcc，MSVC6.0 ...）
While doing source level debugging (using any debugger) does any debugger save state of some iteration/for-loop/any code executed and allow the user to go back to that previously executed code/data state at a later point of time during debugging? The need for this is some variable/pointer is corrupted somewhere earlier in time during execution but is accessed after some time / later in the execution of code and thats when it crashes/hangs the code, so i would like to go back and see which function/at what time the variable was corrupted/wrong value computed and written to it ? Is it possible in any debugger (gcc, MSVC6.0 ...)
是否有任何调试器/ IDE有规定当内存地址/变量被标记对于分析，它应该显示每次更改/写入哪个文件，哪个代码更改了内存（写入）的功能？
Does any debugger/IDE have provision that when a memory address/variable is marked for "analysis", it should display which function in which file, and which code changed that memory(write), every time it is changed/written?
-AD
推荐答案
听起来很可怕，你会想要抓住一个Visual Studio 2010。
It sounds an awful lot like you will want to grab a copy of Visual Studio 2010.
他们正在几乎完全实现你在＃1中描述的内容 - 在Visual Studio团队系统中有一个关于新的历史调试器的屏幕录像2010 on 频道9 。
They are implementing almost exactly what you're describing in #1 - there is a screencast about the new "The Historical Debugger" in Visual Studio Team System 2010 on Channel 9.
在这个条目中有一点更多关于这里（这是2008年4月的代号为Rosario的CTP）
There's a bit more about it in this entry located here (this one is for the April 2008 CTP of codename 'Rosario')
我发现了新定义的历史调试器从Maor David的博客条目（这里）：
I've found this definition of the new Historical Debugger from a blog entry by Maor David (here):
Visual Studio历史调试器捕获并记录应用程序运行时的功能。发生错误时，您可以通过调查历史调试器记录的信息快速查找根本原因。在调试过程中的任何时候，您可以及时向后退，以确定发生错误的地方。
"Visual Studio Historical Debugger captures and records what the application does while it is running. When an error occurs, you can quickly find the root cause by investigating the information that was recorded by the Historical Debugger. At any time during debugging, you can go backward and forward in time to determine where an error occurred."
这是另一个视频演练另外！
编辑：我开始评估最多的（1）Visual Studio 2010的最近的CTP 下降（31/10 - 10月08日），他们似乎有一个早期版本的历史调试器实现，可能值得一试。
I starting evaluating the most (1) recent CTP drop (31/10 - October 08) of Visual Studio 2010 and they seem to have an early version of the historical debugger implemented. It might be worth checking out.
这篇关于向后调试的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
