基于 Web 的跟踪解析器听起来是个好主意。它可以将输出解析为一堆可以折叠的嵌套 ul 和 li 元素。我的时间也很紧张，但如果你愿意合作，请告诉我。
I just using started xdebug today came across this problem a few ahours ago too. I'd love a cachegrind style gui for xdebug traces.
A lot of the lower level calls contain uneccesary information like strlen() calls. I found that xdebug starts the trace file has 21 spaces for top level calls to functions, 23 spaces for second-level calls, 25 and so on. So you can do is grep out lines with more than 22 or more spaces to list top level calls, 24 for sencond and higher level calls etc.
cat trace.xt | grep -v ' '
The web-based trace parser sounds a good idea. It could parse the output into a bunch of nested ul and li elements that could be collapsed. I'm tight for time too, but if you're up for a collaboration lemme know.
You may try Xdebug Trace Explorer. View in Tree-style. I built it after looking around and didn't find any matching solutions. Still not optimize for large file yet:
xdebug.org 上有一个 vim 脚本，可以让你进行“代码折叠”，使它们更容易深入研究，但我从未见过任何可以将该格式解析为任何类型的图形表示的东西。
There's a script for vim at xdebug.org that lets you do 'code folding' to make them a little bit easier to dig into, but I've never seen anything that can parse that format into any kind of graphical representation.
I don't know if this is exactly what you need, but you can enable profiling in XDebug and then dump a big cachegrind file. On my mac, I then used MacCallGrind to view those dumps in a GUI. I can at least see the whole stack of calls for a given request and how much time each call took. Is that what you mean? I haven't got that working in Eclipse PDT yet.
发布评论
评论（10）
我发现这非常可靠。也许它对你也有用：
https://github.com/corretge/xdebug-trace-图形用户界面
I found this to be pretty solid. Maybe it's serviceable to you, too:
https://github.com/corretge/xdebug-trace-gui
大声喊出 http://derickrethans.nl/xdebug-and-tracing-memory-用法.html。不是典型的 GUI，但它确实可以轻松查看数据。
Shout out to http://derickrethans.nl/xdebug-and-tracing-memory-usage.html. Not a typical GUI, but it does make it easy to view the data.
我找到了这个：xdebug 跟踪文件解析器。
I found this one: xdebug trace file parser.
我今天刚使用开始的 xdebug 几个小时前也遇到了这个问题。我想要一个用于 xdebug 跟踪的 Cachegrind 风格的 GUI。
许多较低级别的调用包含不必要的信息，例如 strlen() 调用。我发现xdebug启动跟踪文件有21个空格用于顶级函数调用，23个空格用于二级调用，25个等等。因此，您可以做的是 grep 出具有超过 22 个或更多空格的行来列出顶级调用，24 个空格用于第二个和更高级别的调用等。
基于 Web 的跟踪解析器听起来是个好主意。它可以将输出解析为一堆可以折叠的嵌套 ul 和 li 元素。我的时间也很紧张，但如果你愿意合作，请告诉我。
I just using started xdebug today came across this problem a few ahours ago too. I'd love a cachegrind style gui for xdebug traces.
A lot of the lower level calls contain uneccesary information like strlen() calls. I found that xdebug starts the trace file has 21 spaces for top level calls to functions, 23 spaces for second-level calls, 25 and so on. So you can do is grep out lines with more than 22 or more spaces to list top level calls, 24 for sencond and higher level calls etc.
The web-based trace parser sounds a good idea. It could parse the output into a bunch of nested ul and li elements that could be collapsed. I'm tight for time too, but if you're up for a collaboration lemme know.
我使用 .NET WinForms 编写了一个简单的查看器：
https://github.com/ron- inbar/xdebug-trace-viewer
您需要 Visual Studio（2010 或更高版本）来构建它。
随意定制代码。
I wrote a simple viewer using .NET WinForms:
https://github.com/ron-inbar/xdebug-trace-viewer
You'll need Visual Studio (2010 or later) to build it.
Feel free to customize the code.
您可以尝试 Xdebug Trace Explorer。以树形方式查看。我环顾四周后构建了它，没有找到任何匹配的解决方案。仍未针对大文件进行优化：
https://github.com/tungbi/xdebug-trace-explorer
You may try Xdebug Trace Explorer. View in Tree-style. I built it after looking around and didn't find any matching solutions. Still not optimize for large file yet:
https://github.com/tungbi/xdebug-trace-explorer
xdebug.org 上有一个 vim 脚本，可以让你进行“代码折叠”，使它们更容易深入研究，但我从未见过任何可以将该格式解析为任何类型的图形表示的东西。
There's a script for vim at xdebug.org that lets you do 'code folding' to make them a little bit easier to dig into, but I've never seen anything that can parse that format into any kind of graphical representation.
我相信 Eclipse 的 PDT 插件会导入跟踪日志，并且我知道它可以与 xdebug 集成并进行分析
关于使用 PDT 和 xdebug 的第 1 部分（共 5 部分）
I believe the PDT plugin for Eclipse will import trace logs and I know it can integrate with xdebug and do profiling
Part 1 of 5 on using PDT and xdebug
我不知道这是否正是您所需要的，但您可以在 XDebug 中启用分析，然后转储一个大的缓存研磨文件。然后，在我的 Mac 上，我使用 MacCallGrind 在 GUI 中查看这些转储。我至少可以看到给定请求的整个调用堆栈以及每个调用花费了多少时间。你是这个意思吗？我还没有在 Eclipse PDT 中使用它。
http://www.xdebug.org/docs/profiler
I don't know if this is exactly what you need, but you can enable profiling in XDebug and then dump a big cachegrind file. On my mac, I then used MacCallGrind to view those dumps in a GUI. I can at least see the whole stack of calls for a given request and how much time each call took. Is that what you mean? I haven't got that working in Eclipse PDT yet.
http://www.xdebug.org/docs/profiler
WebGrind 提供了一种通过浏览器查看 CacheGrind 文件的好方法：
但是看看 Facebook 开源的 XHProf，它非常容易设置，捕获许多重要指标，甚至生成调用图：
WebGrind provides a nice, simple way to view CacheGrind files via a browser:
But look at XHProf which is open sourced by Facebook, is very easy to setup, captures many important metrics, and even generates call graphs: