Mark Hills <m...@pogo.org.uk> writes: > I have a pre-compiled .so library, which was given to me for profiling. > > gdb can see a complete call stack -- both the library and my own code, as > expected. > > But in perf the callgraph for the library is not present. I'm using "perf > record -g", and the callgraph for the other code is seen. > > In what cases could gdb see the stack, but perf cannot?
No frame pointer. Recompile with -fno-omit-frame-pointer Or if you have a new enough perf, you can use -g dwarf to enable dwarf backtracing, but it's very slow and also doesn't handle all situations gdb handles. -Andi -- a...@linux.intel.com -- Speaking for myself only -- To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
