Hi, I am trying to use a heap profiling tool, which uses libunwind to get backtraces. I am able to cross-compile libunwind, link it against my simple program and get backtrace using libunwind. However the heap profiler tool is not able to do the same even though it is linked against the same libunwind library and its usage to get the backtrace is similar to mine. The heap profiler code does use various static and inline functions as well as function pointers.
I am wondering if libunwind is not able to get full backtrace on mips64 all the time? I mean does use of certain things (line inline functions, function pointers, static functions) break libunwind? It is only able to get 1 level backtrace. Sincerely, Sid
_______________________________________________ Libunwind-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/libunwind-devel
