本文是小编为大家收集整理的关于Visual Studio剖析器显示"[破碎]"为函数名的处理/解决方法,可以参考本文帮助大家快速定位并解决问题,中文翻译不准确的可切换到English标签页查看源文。
问题描述
我正在尝试介绍我的C ++ DLL,但是Profiler不与我合作.我想看到呼叫树一个启用,但是只有stl函数显示出来,而不是全部不连接 - 当我单击任何功能时,他们的呼叫者是" [brok broken].
我不知道我的Google技能是否还不够,但是我找不到有关[破碎]含义以及如何解决的任何信息.
这是一个调试构建.我不能保证这不是由于某些编译器的设置,但我跌倒了,就像我尝试了所有事情.
应该注意的是,打破代码并添加断点效果很好,因此,探查器只是无法访问此信息
如果它添加了任何信息,请按照指定的特定dll进行分析在这里给出例外"文件不包含数据缓冲区".
推荐答案
我的猜测是输出的PDB有问题(例如,您可以/debug:debug:fastlink在链接器的设置中设置,这会产生仅参考的PDB).
如果不是这种情况,您可以尝试我的Profiriler "> - 我的profiriler - 我用作VisualStudio的扩展,正在仪器(意味着它的功能准确),并在实时显示统计信息.
问题描述
I am trying to profile my c++ dll, but the profiler is not working with me. I would like to see the call tree an so on, but only the stl functions show up, and not all disjoint - when i click on any function, their caller is "[broken]".
I don't know if my google skills are just not sufficient, but i can not find any information on what [broken] means, and how to fix it.
This is a debug build. I cannot guarantee this is not due to some compiler settings, but i fell like i have tried everything.
It should be noted that breaking the code and adding breakpoints works fine, so the profiler just doesn't access this information
If it adds any information, profiling the specific DLL as specified here gives the exception "File contains no data buffers".
推荐答案
My guess is that something wrong with PDBs of your output (for instance, you may have /DEBUG:FASTLINK set in your linker's settings, which produces reference-only PDBs).
If it's not the case, you may try my profiler - it works as an extension to VisualStudio, is instrumenting (meaning it's function-accurate) and displays stats in realtime.