From: Thomas-Mich Richter <tmricht@linux.ibm.com>
To: Martin Vuille <jpmv27@aim.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
brueckner@linux.vnet.ibm.com, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com
Subject: Re: [PATCH] perf test: Adapt test case record+probe_libc_inet_pton.sh for s390
Date: Thu, 26 Apr 2018 10:09:00 +0200 [thread overview]
Message-ID: <151b93fd-8e12-4abf-1e69-329de6eab777@linux.ibm.com> (raw)
In-Reply-To: <25418aa4-60bb-9f16-c880-8caaf8a20931@aim.com>
On 04/25/2018 04:19 PM, Martin Vuille wrote:
> Apologies for any problems my patch may be causing.
>
> I'm unclear on what is the proposed fix, other than reverting the commit.
>
> In the problem scenario, is a --symfs option used? Is the debug info being obtained from the symfs directory?
>
> Unfortunately, I've had to change my focus for the time being, so won't be able to investigate further for a while.
>
> Arnaldo, I'm fine with you reverting this change for now.
>
> Regards,
>
> MV
>
>
Martin,
there is no need to revert the patch. I have adopted the test case for s390 and it
now stops at main, which is identical to x86.
The --symfs option was not used, however the debug file selected for dwarf examination
was different. With you patch it changed from /usr/lib64/libc.so (old) to
/usr/lib/debug/lib64/libc-2.26.so.debug (new)
and I think that this file has not all the info (at least on s390).
--
Thomas Richter, Dept 3303, IBM s390 Linux Development, Boeblingen, Germany
--
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2018-04-26 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 8:19 [PATCH] perf test: Adapt test case record+probe_libc_inet_pton.sh for s390 Thomas Richter
2018-04-12 13:10 ` Arnaldo Carvalho de Melo
2018-04-25 14:19 ` Martin Vuille
2018-04-26 8:09 ` Thomas-Mich Richter [this message]
2018-04-26 13:57 ` Martin Vuille
2018-04-26 15:26 ` Martin Vuille
2018-04-27 7:55 ` Thomas-Mich Richter
2018-04-27 12:31 ` Martin Vuille
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=151b93fd-8e12-4abf-1e69-329de6eab777@linux.ibm.com \
--to=tmricht@linux.ibm.com \
--cc=acme@kernel.org \
--cc=brueckner@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jpmv27@aim.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=schwidefsky@de.ibm.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).