mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	LKML <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Subject: Re: [PATCH v3] perf tools: Introduce perf_thread for backtrace
Date: Wed, 2 Dec 2015 17:27:20 +0100	[thread overview]
Message-ID: <20151202162720.GA11978@krava.brq.redhat.com> (raw)
In-Reply-To: <1449070420-32401-1-git-send-email-namhyung@kernel.org>

On Thu, Dec 03, 2015 at 12:33:40AM +0900, Namhyung Kim wrote:
> Backtrace is a crucial info for debugging.  And upcoming refcnt
> tracking facility also wants to use it.
> 
> So instead of relying on glibc's backtrace_symbols[_fd] which misses
> some (static) functions , use our own symbol searching mechanism.  To
> do that, add perf_thread global variable to keep its maps and symbols.
> 
> The backtrace output from TUI is changed like below.  (I made a key
> action to generate a segfault):
> 
> Before:
>   perf: Segmentation fault
>   -------- backtrace --------
>   perf[0x544a8b]
>   /usr/lib/libc.so.6(+0x33680)[0x7fc46420b680]
>   perf[0x54041b]
>   perf(perf_evlist__tui_browse_hists+0x91)[0x5432e1]
>   perf(cmd_report+0x1d20)[0x43cb10]
>   perf[0x487073]
>   perf(main+0x62f)[0x42cb1f]
>   /usr/lib/libc.so.6(__libc_start_main+0xf0)[0x7fc4641f8610]
>   perf(_start+0x29)[0x42cc39]
> 
> After:
>   perf: Segmentation fault
>   -------- backtrace --------
>   perf_evsel__hists_browse(+0x43b) in perf [0x54066b]
>   perf_evlist__tui_browse_hists(+0x91) in perf [0x543531]
>   cmd_report(+0x1d20) in perf [0x43cb50]
>   run_builtin(+0x53) in perf [0x4870b3]
>   main(+0x634) in perf [0x42cb54]
>   __libc_start_main(+0xf0) in libc-2.22.so [0x7fea3577c610]
>   _start(+0x29) in perf [0x42cc79]
> 
> Cc: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
> v3) check return value of create_perf_thread()

Acked-by: Jiri Olsa <jolsa@kernel.org>

thanks,
jirka

  reply	other threads:[~2015-12-02 16:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02  5:42 [PATCH v2] " Namhyung Kim
2015-12-02  8:16 ` Jiri Olsa
2015-12-02 15:33   ` [PATCH v3] " Namhyung Kim
2015-12-02 16:27     ` Jiri Olsa [this message]
2015-12-03  0:15     ` 平松雅巳 / HIRAMATU,MASAMI
2015-12-03  1:15       ` Namhyung Kim
2015-12-03  7:13         ` 平松雅巳 / HIRAMATU,MASAMI
2015-12-04 13:15           ` Namhyung Kim
2015-12-06  3:36             ` 平松雅巳 / HIRAMATU,MASAMI

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=20151202162720.GA11978@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    /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

all inboxes | Powered by JetHome®