From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Kyeongmin Cho <korea.drzix@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-kernel@vger.kernel.org, Wang Nan <wangnan0@huawei.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH 2/2] perf report: Add gcc option '-rdynamic' to define symbol callchain_param
Date: Thu, 28 Apr 2016 12:26:30 -0300 [thread overview]
Message-ID: <20160428152630.GB3386@kernel.org> (raw)
In-Reply-To: <20160428141216.GB17161@krava>
Em Thu, Apr 28, 2016 at 04:12:16PM +0200, Jiri Olsa escreveu:
> On Thu, Apr 28, 2016 at 10:00:01PM +0900, Kyeongmin Cho wrote:
> > As libperf-gtk.so cannot find out undefined symbol 'callchain_param',
> > '-rdynamic' option is needed to add the symbol to the dynamic symbol
> > table.
>
> hi,
> following command seems to work for me:
> $ perf report --gtk
>
> could you please specify what's failing for you?
I haven't tested this one, but I thought it was legit, as
callchain_param is used in more places now, so perhaps you haven't
updated the gtk.so thing that gets created with the perf gtk UI?
- Arnaldo
next prev parent reply other threads:[~2016-04-28 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 13:00 [PATCH 1/2] perf report: Find lib path correctly for gtk option Kyeongmin Cho
2016-04-28 13:00 ` [PATCH 2/2] perf report: Add gcc option '-rdynamic' to define symbol callchain_param Kyeongmin Cho
2016-04-28 14:12 ` Jiri Olsa
2016-04-28 14:49 ` Kyeongmin Cho
2016-05-01 15:44 ` Jiri Olsa
2016-04-28 15:26 ` Arnaldo Carvalho de Melo [this message]
2016-04-28 14:07 ` [PATCH 1/2] perf report: Find lib path correctly for gtk option Jiri Olsa
2016-04-28 14:35 ` drzix
2016-04-29 11:50 ` Namhyung Kim
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=20160428152630.GB3386@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=korea.drzix@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=wangnan0@huawei.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
Powered by JetHome