Loved it - but needed it to work with pstack output

[lmnca]

Hi Brendan,

I used your flamegraph scripts and found them great! However my stack samples were in a slightly different format than those supported, as they were produced by repeatedly calling pstack at intervals on a process running a gcc-compiled executable coded in C++. I have the modified version of the script which I am willing to contribute, as well as examples of the stack format if you're interested. Please just let me know.

Regards,

Laurent.

[nromito]

Hi Laurent,

Could you provide that script? I think this is an invaluable script to use for flame graphs because a lot of people use linux production environments and most of these environments have easy access to pstack.

Thanks, Nick

[xen0l]

@lmnca could you provide the pstack script?

[lmnca]

@xen01 pstack is usually in /usr/bin/pstack. In my case it is a link to /usr/bin/gstack. In my company we are using CentOs distros.

[yejw5]

@lmnca Did you got a solution？

I have accounted a platform that no perf tool works, only pstack can dump function backtrace.

Many thanks ~

[yejw5]

@lmnca Did you got a solution？

I have accounted a platform that no perf tool works, only pstack can dump function backtrace.

Many thanks ~

I have found stackcollapse-gdb.pl, but it seems that haven't distinguish on/off-cpu?

[randomstuff]

I have found stackcollapse-gdb.pl, but it seems that haven't distinguish on/off-cpu?

Another solution might be to use elfutils stack with stackcollapse-elfutils.pl.

In all three cases, this would include both on-CPU and off-CPU time.