aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorSteven Rostedt <[email protected]>2016-01-29 10:22:41 -0500
committerSteven Rostedt <[email protected]>2016-01-29 12:19:10 -0500
commit6ccd83714a009ee301b50c15f6c3a5dc1f30164c (patch)
treee9b16f16bd6558120805a2d03d2a1dd0db27d2f0 /tools/perf/scripts/python/call-graph-from-postgresql.py
parent92e963f50fc74041b5e9e744c330dca48e04f08d (diff)
tracing/stacktrace: Show entire trace if passed in function not found
When a max stack trace is discovered, the stack dump is saved. In order to not record the overhead of the stack tracer, the ip of the traced function is looked for within the dump. The trace is started from the location of that function. But if for some reason the ip is not found, the entire stack trace is then truncated. That's not very useful. Instead, print everything if the ip of the traced function is not found within the trace. This issue showed up on s390. Link: http://lkml.kernel.org/r/[email protected] Fixes: 72ac426a5bb0 ("tracing: Clean up stack tracing and fix fentry updates") Cc: [email protected] # v4.3+ Reported-by: Heiko Carstens <[email protected]> Tested-by: Heiko Carstens <[email protected]> Signed-off-by: Steven Rostedt <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions