[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <157199317547.8075.1010940983970397945.stgit@devnote2>
Date: Fri, 25 Oct 2019 17:46:15 +0900
From: Masami Hiramatsu <mhiramat@...nel.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Jiri Olsa <jolsa@...hat.com>, Namhyung Kim <namhyung@...nel.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
linux-kernel@...r.kernel.org
Subject: [BUGFIX PATCH 0/6] perf/probe: Additional fixes for range only functions
Hi Arnaldo,
Here are some bugfixes for the bugs you found in previous series
and similar one.
I found that there are some dwarf_entrypc() related bugs in perf
probe and fixed all except one special add-hoc code in
convert_variable_location()(*).
This time I embedded before-and-after examples in each commit.
Please check it how to reproduce it.
(*) This had been introduced for fixup fentry related gcc bug,
see commit 3d918a12a1b3 ("perf probe: Find fentry mcount fuzzed
parameter location") for detail. Nowadays gcc already fixed
this issue and this seems like a dead code. Moreover, it is not
sure such old gcc can generate DIE without entry_pc attribute.
So I decided not to touch it.
Thank you,
---
Masami Hiramatsu (6):
perf/probe: Fix wrong address verification
perf/probe: Fix to probe a function which has no entry pc
perf/probe: Fix to probe an inline function which has no entry pc
perf/probe: Fix to list probe event with correct line number
perf/probe: Fix to show inlined function callsite without entry_pc
perf/probe: Fix to show ranges of variables in functions without entry_pc
tools/perf/util/dwarf-aux.c | 6 +++---
tools/perf/util/probe-finder.c | 40 ++++++++++++++--------------------------
2 files changed, 17 insertions(+), 29 deletions(-)
--
Masami Hiramatsu (Linaro) <mhiramat@...nel.org>
Powered by blists - more mailing lists