From: Kim Phillips <kim.phillips@arm.com>
To: Martin Vuille <jpmv27@aim.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] perf unwind: Report error from dwfl_attach_state
Date: Tue, 20 Mar 2018 08:06:33 +0800 [thread overview]
Message-ID: <20180320080633.10e8414475a534ce9cf26c28@arm.com> (raw)
In-Reply-To: <20180318175053.4222-1-jpmv27@aim.com>
On Sun, 18 Mar 2018 13:50:53 -0400
Martin Vuille <jpmv27@aim.com> wrote:
> In verbose level 2, errors returned by libdw are reported in most cases,
> but not when calling dwfl_attach_state.
>
> Since elfutils v 0.160 (2014), dwfl_attach_state sets the error code to
> report failure cause. On failure, log the reported error.
>
> Signed-off-by: Martin Vuille <jpmv27@aim.com>
> ---
Reviewed-by: Kim Phillips <kim.phillips@arm.com>
Kim
next prev parent reply other threads:[~2018-03-20 0:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 17:50 [PATCH RESEND] perf unwind: Report error from dwfl_attach_state Martin Vuille
2018-03-20 0:06 ` Kim Phillips [this message]
2018-03-20 16:18 ` Arnaldo Carvalho de Melo
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=20180320080633.10e8414475a534ce9cf26c28@arm.com \
--to=kim.phillips@arm.com \
--cc=acme@redhat.com \
--cc=jpmv27@aim.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.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;
as well as URLs for NNTP newsgroup(s).