Visual Studio Profiler 显示“[损坏]"作为函数名 [英] Visual Studio Profiler showing "[broken]" as function names

查看:15
本文介绍了Visual Studio Profiler 显示“[损坏]"作为函数名的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试分析我的 c++ dll,但分析器无法与我一起使用.我想查看调用树等等,但只有 stl 函数显示,而且并非全部不相交 - 当我点击任何函数时,它们的调用者是[broken]".

我不知道我的 google 技能是否不够,但我找不到任何关于 [broken] 意味着什么以及如何修复它的信息.

这是一个调试版本.我不能保证这不是由于某些编译器设置造成的,但我觉得我什么都试过了.

需要注意的是,中断代码和添加断点可以正常工作,所以分析器只是不访问这些信息

如果它添加任何信息,则按指定分析特定 DLL

解决方案

我的猜测是您的输出的 PDB 有问题(例如,您可能在链接器的设置中设置了/DEBUG:FASTLINK,这会产生仅供参考PDB).

如果不是这样,您可以尝试 我的分析器 - 它作为 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.

这篇关于Visual Studio Profiler 显示“[损坏]"作为函数名的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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