RajivKurian

Here is a minimal program and the folded stack trace [vec.txt](https://github.com/brendangregg/FlameGraph/files/945146/vec.txt) [out.perf-folded.txt](https://github.com/brendangregg/FlameGraph/files/945152/out.perf-folded.txt) Both files are attached as .txt because github won't allow .cpp or .perf-folded extensions.

Also attaching the raw perf script file, in case it's useful [perf_script_output_file.txt](https://github.com/brendangregg/FlameGraph/files/945178/perf_script_output_file.txt)

I noticed that the folded file and the output of perf_script look exactly the same (which might be the problem).

I think I see the problem: ``` cat perf_script_output_file.txt | FlameGraph/stackcollapse-perf.pFlameGraph/stackcollapse-perf.pl line 1: :6062: command not found FlameGraph/stackcollapse-perf.pl: line 2: syntax error near unexpected token `(' FlameGraph/stackcollapse-perf.pl: line 2: `...

I did not. On Mon, Apr 23, 2018 at 9:00 AM John Krull wrote: > @RajivKurian did you ever find a > solution to your problem? > > — >...

Yeah, looking at godbolt's solution would be my suggestion too. An alternative might be to have a few selectable options like -march=native etc, like you do for optimization level. Thanks!...