From: Florian Weimer <fweimer@redhat.com>
To: "Miller, Tim" <theosib@amazon.com>
Cc: "Miller, Tim via Libc-help" <libc-help@sourceware.org>
Subject: Re: Build glibc for aarch64 with C-only versions of memcpy?
Date: Wed, 15 Dec 2021 22:33:46 +0100 [thread overview]
Message-ID: <87h7b9pn7p.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <FBE8C555-1678-4FE2-A725-6B11BF159D2D@amazon.com> (Tim Miller's message of "Wed, 15 Dec 2021 21:28:04 +0000")
* Tim Miller:
> Are you referring to the LBR mode that perf supports?
Not just that. There are other call graph modes. For example, you
could use a distribution that builds everything with DWARF unwinding
data, and use DWARF unwinding.
> Well, I tried that, but it keeps stopping at that breakpoint over and
> over again. I do get a stack trace, but what I need to find out is who
> is calling it MOST.
Don't set a breakpoint. Just hit ^C from time to time to see if you can
hit the function. But at 3% to 4%, this isn't going to work or is very
tedious.
Thanks,
Florian
next prev parent reply other threads:[~2021-12-15 21:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 20:31 Miller, Tim
2021-12-15 20:40 ` Florian Weimer
2021-12-15 21:13 ` Miller, Tim
2021-12-15 21:28 ` Miller, Tim
2021-12-15 21:33 ` Florian Weimer [this message]
2021-12-15 21:37 ` Miller, Tim
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=87h7b9pn7p.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-help@sourceware.org \
--cc=theosib@amazon.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).