From: ahmadkhorrami <ahmadkhorrami@ut.ac.ir>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Linux-trace Users <linux-trace-users@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-trace-users-owner@vger.kernel.org,
Jin Yao <yao.jin@linux.intel.com>,
Milian Wolff <milian.wolff@kdab.com>,
Namhyung Kim <namhyung@kernel.org>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: Wrong Perf Backtraces
Date: Sun, 29 Mar 2020 17:09:33 +0430 [thread overview]
Message-ID: <ff979b3fffc8222d8da848b8cb92f77c@ut.ac.ir> (raw)
In-Reply-To: <20200329120816.GD2155755@krava>
Thanks. I did both of your changes. Perhaps some outputs are revised.
But I still have repeated function calls and the script detects them.
Here is one of them when the sampling period is 1000 events:
evince 8751 2605.226573: 10000
mem_load_uops_retired.l3_miss:uppp: 5635f8c4cf3a 5080022
N/A|SNP N/A|TLB N/A|LCK N/A
7f91785a737d gtk_box_forall+0x2d
(/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.30) gtkbox.c:0
7f91788120b5 gtk_widget_propagate_state+0x195
(/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.30) gtkwidget.c:0
7f91785a73cf gtk_box_forall+0x7f
(/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.30) gtkbox.c:0
7f91788120b5 gtk_widget_propagate_state+0x195
(/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.30) gtkwidget.c:0
7f917875ebcf gtk_stack_forall+0x2f
(/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.30) gtkstack.c:0
7f91788120b5 gtk_widget_propagate_state+0x195
(/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.30) gtkwidget.c:0
7f91788120b5 gtk_widget_propagate_state+0x195
(/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.30) gtkwidget.c:0
7f91788154aa gtk_window_forall+0x3a
(/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.30) gtkwindow.c:0
7f91788120b5 gtk_widget_propagate_state+0x195
(/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.30) gtkwidget.c:0
7f9178812a2d gtk_widget_update_state_flags+0x5d
(/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.30) gtkwidget.c:0
7f917881919e gtk_window_state_event+0x21e
(/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.30) gtkwindow.c:0
5635f6fd53ce ev_window_state_event+0x5e
(/opt/evince-3.28.4/bin/evince) ev-window.c:4410
7f91786b87fa _gtk_marshal_BOOLEAN__BOXED+0x6a
(/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.30)
7f9176b9410c g_closure_invoke+0x19c
(/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.5600.4)
7f9176ba6de7 signal_emit_unlocked_R+0xcd7
(/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.5600.4) gsignal.c:0
7f9176baf0ae g_signal_emit_valist+0x40e
(/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.5600.4)
7f9176bb012e g_signal_emit+0x8e
(/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.5600.4)
7f9178800533 gtk_widget_event_internal+0x163
(/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.30) gtkwidget.c:0
7f91786b78cd gtk_main_do_event+0x77d
(/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.30)
7f91781c8764 _gdk_event_emit+0x24
(/usr/lib/x86_64-linux-gnu/libgdk-3.so.0.2200.30)
7f91781f8f91 gdk_event_source_dispatch+0x21
(/usr/lib/x86_64-linux-gnu/libgdk-3.so.0.2200.30) gdkeventsource.c:0
7f91768b9416 g_main_context_dispatch+0x2e6
(/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.5600.4)
7f91768b964f g_main_context_iterate.isra.26+0x1ff
(/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.5600.4) gmain.c:0
7f91768b96db g_main_context_iteration+0x2b
(/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.5600.4)
7f9176e7ae3c g_application_run+0x1fc
(/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.5600.4)
5635f6fbc707 main+0x447 (/opt/evince-3.28.4/bin/evince)
main.c:316
7f9175ee0b96 __libc_start_main+0xe6
(/lib/x86_64-linux-gnu/libc-2.27.so) libc-start.c:310
5635f6fbc899 _start+0x29 (/opt/evince-3.28.4/bin/evince)
Here, we have two consecutive "7f91788120b5
gtk_widget_propagate_state+0x195
(/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.30) gtkwidget.c:0" lines,
while "gtk_widget_propagate_state+0x195" is not recursive. It should
call "gtk_container_forall", which does not occur even after the second
(inner) call.
Regards.
On 2020-03-29 16:38, Jiri Olsa wrote:
> On Sun, Mar 29, 2020 at 04:22:27PM +0430, ahmadkhorrami wrote:
>
>> Hi,
>> Thanks. Still no change. Sorry, I forgot to say that you should
>> initialize
>> the "perfCMD" variable to your perf binary path.
>
> sure I did that, and your script detected the double entries,
> now when we show also srcline for them it's silent
>
> so there's no change at all for your perf script output?
>
> jirka
>
> Regards.
>
> On 2020-03-29 15:49, Jiri Olsa wrote:
>
> On Sun, Mar 29, 2020 at 05:46:57AM +0430, ahmadkhorrami wrote:
>
> Hi,
> Each line is correct. I mean addresses match symbols. But some
> callers and
> callees do not match. Perhaps callchain misses some callers in
> between.
> Regards
> right, I missed another case.. how about the change below?
> your script is silent now on my data
>
> jirka
>
> ---
> diff --git a/tools/perf/util/evsel_fprintf.c
> b/tools/perf/util/evsel_fprintf.c
> index 3b4842840db0..fc4fb88937ed 100644
> --- a/tools/perf/util/evsel_fprintf.c
> +++ b/tools/perf/util/evsel_fprintf.c
> @@ -173,6 +173,8 @@ int sample__fprintf_callchain(struct perf_sample
> *sample, int left_alignment,
>
> if (print_srcline)
> printed += map__fprintf_srcline(map, addr, "\n ", fp);
> + else if (node->srcline)
> + printed += fprintf(fp, " %s", node->srcline);
>
> if (sym && sym->inlined)
> printed += fprintf(fp, " (inlined)");
next prev parent reply other threads:[~2020-03-29 12:39 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <157597d74ff17f781d9de7e7e3defd13@ut.ac.ir>
2020-03-22 20:24 ` Wrong Perf Backtraces ahmadkhorrami
2020-03-23 0:34 ` Steven Rostedt
[not found] ` <21b3df4080709f193d62b159887e2a83@ut.ac.ir>
2020-03-23 8:49 ` Jiri Olsa
2020-03-23 10:03 ` ahmadkhorrami
2020-03-25 15:18 ` ahmadkhorrami
2020-03-25 15:46 ` Jiri Olsa
2020-03-25 18:54 ` ahmadkhorrami
2020-03-25 18:58 ` Arnaldo Carvalho de Melo
2020-03-25 19:10 ` ahmadkhorrami
2020-03-25 19:28 ` Arnaldo Carvalho de Melo
2020-03-25 20:01 ` ahmadkhorrami
2020-03-25 20:39 ` Jiri Olsa
2020-03-25 21:02 ` Jiri Olsa
2020-03-25 21:09 ` Steven Rostedt
2020-03-25 21:37 ` ahmadkhorrami
2020-03-25 21:46 ` Jiri Olsa
2020-03-25 22:21 ` ahmadkhorrami
2020-03-25 23:09 ` ahmadkhorrami
2020-03-26 9:59 ` Jiri Olsa
2020-03-26 13:20 ` ahmadkhorrami
2020-03-26 15:39 ` Jiri Olsa
2020-03-26 18:19 ` ahmadkhorrami
2020-03-26 18:21 ` ahmadkhorrami
2020-03-27 9:20 ` Jiri Olsa
2020-03-27 10:59 ` ahmadkhorrami
2020-03-27 11:04 ` ahmadkhorrami
2020-03-27 12:10 ` Milian Wolff
2020-03-27 12:58 ` ahmadkhorrami
2020-03-27 13:25 ` Milian Wolff
2020-03-27 13:33 ` ahmadkhorrami
2020-03-27 18:43 ` ahmadkhorrami
2020-03-27 22:37 ` Jiri Olsa
2020-03-27 23:12 ` ahmadkhorrami
2020-03-28 23:34 ` Jiri Olsa
2020-03-29 0:43 ` ahmadkhorrami
2020-03-29 1:16 ` ahmadkhorrami
2020-03-29 11:19 ` Jiri Olsa
2020-03-29 11:52 ` ahmadkhorrami
2020-03-29 12:08 ` Jiri Olsa
2020-03-29 12:39 ` ahmadkhorrami [this message]
2020-03-29 13:50 ` Milian Wolff
2020-03-29 14:23 ` ahmadkhorrami
2020-03-29 19:20 ` Jiri Olsa
2020-03-30 6:09 ` Milian Wolff
2020-03-30 13:07 ` Jiri Olsa
2020-03-30 13:49 ` ahmadkhorrami
2020-03-30 19:05 ` ahmadkhorrami
2020-03-30 21:05 ` debuginfod-based dwarf downloading, was " Frank Ch. Eigler
2020-03-31 9:26 ` Jiri Olsa
2020-03-31 14:00 ` Frank Ch. Eigler
2020-03-31 4:43 ` ahmadkhorrami
2020-03-31 9:30 ` Jiri Olsa
2020-03-31 11:53 ` ahmadkhorrami
2020-03-31 12:43 ` ahmadkhorrami
2020-03-31 13:20 ` Jiri Olsa
2020-03-31 13:39 ` ahmadkhorrami
2020-03-31 14:44 ` Milian Wolff
2020-03-31 15:02 ` ahmadkhorrami
2020-03-31 15:05 ` ahmadkhorrami
2020-03-31 15:29 ` Milian Wolff
2020-03-31 16:10 ` Arnaldo Carvalho de Melo
2020-03-31 19:20 ` ahmadkhorrami
2020-03-31 19:17 ` ahmadkhorrami
2020-03-31 20:57 ` ahmadkhorrami
2020-04-04 1:01 ` ahmadkhorrami
2020-04-11 16:42 ` ahmadkhorrami
2020-04-11 21:04 ` ahmadkhorrami
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff979b3fffc8222d8da848b8cb92f77c@ut.ac.ir \
--to=ahmadkhorrami@ut.ac.ir \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-trace-users-owner@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=milian.wolff@kdab.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=yao.jin@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).