在断点处保留信息的调试工具(例如,调用堆栈和变量值) [英] Debugging Tool that Retains Information at Breakpoints (e.g. Call Stacks and Variable Values)

查看:122
本文介绍了在断点处保留信息的调试工具(例如,调用堆栈和变量值)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在某些情况下难以单步调试代码进行调试。想知道,是否有可用的调试工具可以在软件中的已识别位置保存调用堆栈/变量信息(例如书签或断点)?在
执行之后,我可以选择所识别的感兴趣位置,询问调用堆栈,并且对于调用堆栈中的每个条目,导航到源代码位置并查看变量值。这是个梦想吗?不幸的是,解决基本的
问题仍然是目前的选择。

I am having difficulty stepping through the code in some cases for debugging. Wondering, is there a debugging tool available that will save call stack/variable information at identified locations in the software (e.g. bookmark or like a breakpoint)? After execution, I could then select the identified location of interest, interrogate the call stack(s) and for each entry in the call stack navigate to the source code location and see the variable values. Is this a pipe dream? Unfortunately, solving the underlying issue of stepping through the code is not an option currently.

谢谢,

Alan

推荐答案

你好Alan,

hello Alan,

我不知道细节,但我怀疑WinDbg可以帮助你实现的目标。 我使用WinDbg来解决asp.net崩溃问题,这种情况与你所描述的情况不同,但是从查看WinDbg文档来看,可能只需要b $ b就可以做你想做的事情。

I don't know the details but I suspect WinDbg might be able to help with what you are trying to achieve.  I used WinDbg for a asp.net crash situation which is different than what you are describing but from looking at the WinDbg documentation, it might be able to do what you want.

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugging-using-windbg

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugging-using-windbg


这篇关于在断点处保留信息的调试工具(例如,调用堆栈和变量值)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆