From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH 1/2] perf symbols: use .gnu_debuglink as gdb does
Date: Wed, 8 Feb 2017 09:27:53 -0300 [thread overview]
Message-ID: <20170208122753.GB6668@kernel.org> (raw)
In-Reply-To: <20170119095139.ya2uxisldfhlfjci@pengutronix.de>
Em Thu, Jan 19, 2017 at 10:51:39AM +0100, Uwe Kleine-König escreveu:
> On Thu, Jul 21, 2016 at 11:48:31AM +0200, Uwe Kleine-König wrote:
> > As documented in the comment gdb looks for debug files not only relative
> > to the binary's directory, but also in .debug and /usr/lib/debug/.
> > Let perf do the same thing.
> >
> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
>
> ping.
Sorry, completely lost track of these two :-\
Applied 'perf probe --symfs' one, the other should be already dealt with
by another patch, this one:
t 9343e45bf6cc4a05f6e271e9f8d06bc87875c604
Author: Matija Glavinic Pecotic <matija.glavinic-pecotic.ext@nokia.com>
Date: Tue Jan 17 15:50:35 2017 +0100
perf unwind: Fix looking up dwarf unwind stack info
-----------
That is in tip/perf/core now.
- Arnaldo
> Best regards
> Uwe
>
> --
> Pengutronix e.K. | Uwe Kleine-König |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2017-02-08 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 9:48 [PATCH 1/2] perf symbols: use .gnu_debuglink as gdb does Uwe Kleine-König
2016-07-21 9:48 ` [PATCH 2/2] perf probe: Add option --symfs Uwe Kleine-König
2017-01-19 9:51 ` [PATCH 1/2] perf symbols: use .gnu_debuglink as gdb does Uwe Kleine-König
2017-02-08 12:27 ` Arnaldo Carvalho de Melo [this message]
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=20170208122753.GB6668@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.