On Mon, 18 Oct 2021, 11:18 Dongliang Mu, <[email protected]> wrote:
> +Brendan Gregg > Good catch! Take a look at his "System Performance, 2nd ed., ISBN 978-0-13-682015-4. He has an interesting blog at https://www.brendangregg.com/blog/index.html As Greg, Pavel, and I said, use GDB if you need it. However I'd still consider using the "func_graph" tracer of ftrace in order to know where to attach GDB in the calls chain. With ftrace you'll also get info about which CPU is running (you wrote that you need to know this information). Now I recall that, by using Perf, somehow I was able to go interactively down to the assembly code and see where it was stuck in an endless loop. Unfortunately at this moment I cannot remember how I did that and I cannot try to reproduce it for you because these days I'm away from my PC (I'm writing with a smartphone). Please try to figure it out by your own. Regards, Fabio > >
_______________________________________________ Kernelnewbies mailing list [email protected] https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
