All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Thomas Richter <tmricht@linux.ibm.com>
Cc: "linux-perf-use." <linux-perf-users@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Sven Schnelle <svens@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Stefan Liebler <stli@linux.ibm.com>
Subject: Re: perf test case probe libc fails with latest Fedora34 glibc update, more info
Date: Tue, 29 Jun 2021 23:01:26 +0900	[thread overview]
Message-ID: <20210629230126.9b8d0d11bafbaa78d68a57ee@kernel.org> (raw)
In-Reply-To: <d689e8e0-64da-e3c6-bc3b-50d4d3a4ee03@linux.ibm.com>

On Tue, 29 Jun 2021 09:21:19 +0200
Thomas Richter <tmricht@linux.ibm.com> wrote:

> On 6/29/21 7:02 AM, Masami Hiramatsu wrote:
> > On Fri, 25 Jun 2021 12:43:29 +0200
> > Thomas Richter <tmricht@linux.ibm.com> wrote:
> > 
> 
> Masami,
> 
> here is more info on this issue:
> 
> # nm /usr/lib64/libc-2.33.so 
> 00000000000a7f30 t __GI_memchr
> 00000000000a3730 t __GI_memcmp
> 00000000000a37e0 t __GI_memcpy
> 00000000000a39a0 t __GI_memmove
> 00000000000a37d0 t __GI_mempcpy
> 00000000000a8000 t __GI___rawmemchr
> 00000000000a6070 t __GI_stpcpy
> 000000000009d190 t __GI___strcasecmp_l
> 00000000000a67a0 t __GI_strcat
> 00000000000a6ec0 t __GI_strchr
> 00000000000a6b70 t __GI_strcmp
> 00000000000a5f70 t __GI_strcpy
> 00000000000a7c70 t __GI_strcspn
> 00000000000a5ad0 t __GI_strlen
> 000000000009d200 t __GI___strncasecmp_l
> 00000000000a6ce0 t __GI_strncmp
> 00000000000a62a0 t __GI_strncpy
> 00000000000a5d30 t __GI_strnlen
> 00000000000a73e0 t __GI_strrchr
> 00000000000b8e80 t __GI_wmemchr
> 0000000000111f60 T __memcpy_chk
> 0000000000111f80 T __memmove_chk
> 0000000000112040 T __stpcpy_chk
> 0000000000112100 T __strcpy_chk
> # 
> 
> These are the entries in the .symtab section and can be used by perf:
> # ./perf probe -vvv -f -x /usr/lib64/libc-2.33.so -a __strcpy_chk

Are there any output of the perf probe? It may report that the
event is found by map (symbol) or debuginfo.

> # ./perf probe -l
>   probe_libc:__strcpy_chk (on __strcpy_chk@debug/strcpy_chk.c in /usr/lib64/libc-2.33.so)
> [root@t35lp46 perf]# 

Thanks! So at least the symbols in .symtab works.

> 
> Hope this helps
> -- 
> Thomas Richter, Dept 3303, IBM s390 Linux Development, Boeblingen, Germany
> --
> Vorsitzender des Aufsichtsrats: Gregor Pillen
> Geschäftsführung: Dirk Wittkopp
> Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294


-- 
Masami Hiramatsu <mhiramat@kernel.org>

      reply	other threads:[~2021-06-29 14:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23 14:21 perf test case probe libc fails with latest Fedora34 glibc update Thomas Richter
2021-06-25 10:34 ` Jiri Olsa
2021-06-25 10:57   ` Thomas Richter
2021-06-25 10:43 ` Part 2: " Thomas Richter
2021-06-29  5:02   ` Masami Hiramatsu
2021-06-29  6:42     ` Thomas Richter
2021-06-29 14:06       ` Masami Hiramatsu
2021-06-30 16:02       ` Masami Hiramatsu
2021-07-02  0:41         ` Masami Hiramatsu
2021-06-29  7:21     ` perf test case probe libc fails with latest Fedora34 glibc update, more info Thomas Richter
2021-06-29 14:01       ` Masami Hiramatsu [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=20210629230126.9b8d0d11bafbaa78d68a57ee@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=acme@kernel.org \
    --cc=hca@linux.ibm.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=stli@linux.ibm.com \
    --cc=svens@linux.ibm.com \
    --cc=tmricht@linux.ibm.com \
    --subject='Re: perf test case probe libc fails with latest Fedora34 glibc update, more info' \
    /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

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.