C profiler/tracer with timeline view
I am trying to get into C language and looking for a profiler or tracer tool that supports timeline view representation with every function calls. Something like tracing via PHP xDebug. Where all function calls placed approximately at exact time they were called in the stack.
My research so far is:
So far I found that valgrind --tool=callgrind ./myscript is the closest one I can use.
However the visualization is a flamegraph that samples the C function calls.
In my case it is a good start for reverse engineering but I would like to have detailed timeline with actual calls timiestamps.
I also checked the gprofng however the textual visualization is not that easy to read and it seems to be same sampled flamegraph
I also tried to do something via perf but it looks like perf recording only system/linux calls without timestamps, at least that what is visible in the speedscope.
Maybe I am not using perf correctly but that is what I got after trying different commands from https://www.brendangregg.com/perf.html
I understand some basics that the app must be compiled with -g or that tracing adds some overhead and timings might be not 100% accurate but I found it difficult to get a tool that can visualize calltree as timeline in C language.
For now the best thing that solves my case is uftrace profiler https://github.com/namhyung/uftrace
- What does it mean when the same source code gives different answers under two different compilers?
- What does this inline-assembly code snippet in Valgrind mean?
- C: Segmantation fault (core dumped)
- Valgrind: how to find the stack variable that is detected as not initalized?
- How does optimization trip valgrind false positives?
- valgrind and std::unique_ptr --- false positive or not?
- valgrind alters binary behaviour
- char** in function C and valgrind conditional jump erro
- Determining if a memory leak is a false positive
- Program crashes valgrind only in Qt Creator
- Set callgrind as default tool of valgrind
- Why does this std::weak_ptr apparently prevent freeing memory, and how can I detect this bug?
- Valgrind: disable conditional jump (or whole library) check
- Segmentation fault when converting char * to char **
- Which Valgrind tool and option to use for investigation of RAM allocation for each function?
- Valgrind gives an error "Invalid read of size 4"
- Is boost::filesystem thread-safe?
- Why does Valgrind report "uninitialized value" but not "invalid read" in my C++ vector access?
- Make a valgrind error suppression generic for a system call
- Is there a emacs valgrind interface?
- Are there known false positives issues with Valgrind?
- How to get the full call stack from Valgrind?
- Mergesort for singly-linked lists gives correct results but leaks memory
- Valgrind Massif - startpoint for memory allocation [cpp]
- Valgrind complain after modifing reference return variable from a vector in c++
- valgrind reporting invalid read with std::string
- How to safely implement "Using Uninitialized Memory For Fun And Profit"?
- Should I worry about "Conditional jump or move depends on uninitialised value(s)"?
- Valgrind: invalid read of size 4 -> sigsegv, works fine without valgrind and in visual studio
- Enable/disable flags when doing a valgrind build