All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Vuille <jpmv27@aim.com>
To: Thomas-Mich Richter <tmricht@linux.ibm.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 09:57:08 -0400	[thread overview]
Message-ID: <daaa4338-0e78-d11c-8699-5b432db6993e@aim.com> (raw)
In-Reply-To: <151b93fd-8e12-4abf-1e69-329de6eab777@linux.ibm.com>



On 04/26/18 04:09, Thomas-Mich Richter wrote:
>
> 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,

Thanks for the additional information. My change was intended to only affect
the case where a --symfs option is used, so your finding is surprising.

I'll take a look to see why this is happening.

Regards,
MV

  reply	other threads:[~2018-04-26 13:57 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
2018-04-26 13:57       ` Martin Vuille [this message]
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=daaa4338-0e78-d11c-8699-5b432db6993e@aim.com \
    --to=jpmv27@aim.com \
    --cc=acme@kernel.org \
    --cc=brueckner@linux.vnet.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tmricht@linux.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 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.