From: Florian Weimer <fweimer@redhat.com>
To: qiu_qiu <linuxfighting@163.com>, libc-help@sourceware.org
Subject: Re: "perf record" has no samples when glibc-debuginfo installed
Date: Thu, 29 Mar 2018 08:41:00 -0000 [thread overview]
Message-ID: <dbf1b3eb-1f9d-a441-2328-a19863f5e0c4@redhat.com> (raw)
In-Reply-To: <116833e0.3e23.1626fa6047c.Coremail.linuxfighting@163.com>
On 03/29/2018 04:46 AM, qiu_qiu wrote:
> "perf record" has no samples on fedora 27 when installed glibc-debuginfo package
>
>
> How reproducible:
>
>
> Steps to Reproduce:
> 1. debuginfo-install glibc
> 2. perf probe -x /lib64/libc.so.6 malloc
> 3. perf record -e probe_libc:malloc -a ls
The probes appear to be there:
# stap -r 4.15.12-301.fc27.x86_64 -L
'process("/lib64/libc.so.6").mark("*")'
process("/usr/lib64/libc-2.26.so").mark("lll_lock_wait_private") $arg1:long
process("/usr/lib64/libc-2.26.so").mark("longjmp") $arg1:long $arg2:long
$arg3:long
process("/usr/lib64/libc-2.26.so").mark("longjmp_target") $arg1:long
$arg2:long $arg3:long
process("/usr/lib64/libc-2.26.so").mark("memory_arena_new") $arg1:long
$arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_arena_retry") $arg1:long
$arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_arena_reuse") $arg1:long
$arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_arena_reuse_free_list")
$arg1:long
process("/usr/lib64/libc-2.26.so").mark("memory_arena_reuse_wait")
$arg1:long $arg2:long $arg3:long
process("/usr/lib64/libc-2.26.so").mark("memory_calloc_retry") $arg1:long
process("/usr/lib64/libc-2.26.so").mark("memory_heap_free") $arg1:long
$arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_heap_less") $arg1:long
$arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_heap_more") $arg1:long
$arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_heap_new") $arg1:long
$arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_malloc_retry") $arg1:long
process("/usr/lib64/libc-2.26.so").mark("memory_mallopt") $arg1:long
$arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_mallopt_arena_max")
$arg1:long $arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_mallopt_arena_test")
$arg1:long $arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_mallopt_free_dyn_thresholds")
$arg1:long $arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_mallopt_mmap_max")
$arg1:long $arg2:long $arg3:long
process("/usr/lib64/libc-2.26.so").mark("memory_mallopt_mmap_threshold")
$arg1:long $arg2:long $arg3:long
process("/usr/lib64/libc-2.26.so").mark("memory_mallopt_mxfast")
$arg1:long $arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_mallopt_perturb")
$arg1:long $arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_mallopt_top_pad")
$arg1:long $arg2:long $arg3:long
process("/usr/lib64/libc-2.26.so").mark("memory_mallopt_trim_threshold")
$arg1:long $arg2:long $arg3:long
process("/usr/lib64/libc-2.26.so").mark("memory_memalign_retry")
$arg1:long $arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_realloc_retry")
$arg1:long $arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_sbrk_less") $arg1:long
$arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_sbrk_more") $arg1:long
$arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_tunable_tcache_count")
$arg1:long $arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_tunable_tcache_max_bytes")
$arg1:long $arg2:long
process("/usr/lib64/libc-2.26.so").mark("memory_tunable_tcache_unsorted_limit")
$arg1:long $arg2:long
process("/usr/lib64/libc-2.26.so").mark("setjmp") $arg1:long $arg2:long
$arg3:long
But they use "memory", not "malloc" for some reason.
Thanks,
Florian
prev parent reply other threads:[~2018-03-29 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 2:46 qiu_qiu
2018-03-29 8:41 ` Florian Weimer [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=dbf1b3eb-1f9d-a441-2328-a19863f5e0c4@redhat.com \
--to=fweimer@redhat.com \
--cc=libc-help@sourceware.org \
--cc=linuxfighting@163.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 read-only IMAP folder(s) and NNTP newsgroup(s).